Main Page

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>TechPubs Wiki</sitename>
    <dbname>techpubs_wiki</dbname>
    <base>http://www.tech-pubs.net/wiki/Main_Page</base>
    <generator>MediaWiki 1.43.0</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">TechPubs Wiki</namespace>
      <namespace key="5" case="first-letter">TechPubs Wiki talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
      <namespace key="828" case="first-letter">Module</namespace>
      <namespace key="829" case="first-letter">Module talk</namespace>
    </namespaces>
  </siteinfo>
<page arvcontinue="">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1</id>
    <timestamp>2025-02-04T03:53:57Z</timestamp>
    <contributor>
      <username>MediaWiki default</username>
      <id>2</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="755" xml:space="preserve">&lt;strong&gt;MediaWiki has been installed.&lt;/strong&gt;

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]</text>
    <sha1>11cef88175cf81168a86e7c0327a5b2d7a1920f5</sha1>
  </revision>
  <revision>
    <id>3</id>
    <parentid>1</parentid>
    <timestamp>2025-02-04T05:53:53Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Base setup</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2294" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Category 1''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt; '''Category 2''' &lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;br /&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[Official Literature|Category 3]]''' &lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[Template:News|News]]''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					{{news}}
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Cat 4''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>a63ef057d0ef1bbbefc4c8470d5cedf124df7045</sha1>
  </revision>
  <revision>
    <id>4</id>
    <parentid>3</parentid>
    <timestamp>2025-02-04T19:17:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2235" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Category 1''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt; '''Category 2''' &lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;br /&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[Official Literature|Category 3]]''' &lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[Template:News|News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Cat 4''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>564e4aaa93c17b8953fb9d827480589ed952a0f0</sha1>
  </revision>
  <revision>
    <id>7</id>
    <parentid>4</parentid>
    <timestamp>2025-02-04T19:32:45Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2233" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Category 1''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt; '''Category 2''' &lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;br /&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[Category 3]]''' &lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>9e0a521f984475a6f678560040f6b2c095e694c7</sha1>
  </revision>
  <revision>
    <id>18</id>
    <parentid>7</parentid>
    <timestamp>2025-02-05T04:42:00Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2675" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				• [[IRIX 101]]&lt;/div&gt;• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]&lt;blockquote&gt;• [[Onyx]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/blockquote&gt;&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Software''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>bd1a5ba3caddd92bf5454cc9b3e4a8ffed262eb8</sha1>
  </revision>
  <revision>
    <id>19</id>
    <parentid>18</parentid>
    <timestamp>2025-02-05T04:42:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2667" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				• [[IRIX 101]]&lt;/div&gt;• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/blockquote&gt;&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>652dc7fa3047bd13145218b7873d1b58440f00d6</sha1>
  </revision>
  <revision>
    <id>34</id>
    <parentid>19</parentid>
    <timestamp>2025-02-05T18:27:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2654" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				• [[IRIX 101]]&lt;/div&gt;• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>a5b525a0816219f6cf76ba9f07815115801f1558</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>MediaWiki:Common.css</title>
  <ns>8</ns>
  <id>2</id>
  <revision>
    <id>2</id>
    <timestamp>2025-02-04T05:11:00Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "/* Prevent line breaks in silly places:     1) Links when we don't want them to    2) Bold "links" to the page itself    2) HTML formulae    3) Ref tags with group names &lt;ref group="Note"&gt; --&gt; "[Note 1]" */  /* Wikipedia CSS */ /* &lt;source lang="css"&gt; */ /* Main page fixes */  #interwiki-completelist {     font-weight: bold; }  div#content .printfooter {     display: none; }  .page-Touhou_Wiki h1.firstHeading {     display: none; }  .page-Touhou_Wiki div#siteNotice {..."</comment>
    <model>css</model>
    <format>text/css</format>
    <text bytes="38969" xml:space="preserve">/* Prevent line breaks in silly places: 
   1) Links when we don't want them to
   2) Bold "links" to the page itself
   2) HTML formulae
   3) Ref tags with group names &lt;ref group="Note"&gt; --&gt; "[Note 1]"
*/

/* Wikipedia CSS */
/* &lt;source lang="css"&gt; */
/* Main page fixes */

#interwiki-completelist {
    font-weight: bold;
}

div#content .printfooter {
    display: none;
}

.page-Touhou_Wiki h1.firstHeading {
    display: none;
}

.page-Touhou_Wiki div#siteNotice {
    width: 70%;
    left: 0;
}

.fundologohib {
    background: url("https://onsen.touhouwiki.net/images/9/96/Patchlogo-transparencia.png");
}

/* Edit window toolbar */

#toolbar {
    height: 22px;
    margin-bottom: 6px;
}

/* Margins for &lt;ol&gt; and &lt;ul&gt; */

#content ol, #content ul, #mw_content ol, #mw_content ul {
    margin-bottom: 0.5em;
}
 
/* Make the list of references in [[Template:Reflist]] smaller */

.references-small {
    font-size: 90%;
}
 
/* Highlight clicked reference in blue to help navigation */

ol.references &gt; li:target, sup.reference:target, span.citation:target {
    background-color: #def;
}
 
/* Ensure refs in table headers and the like aren't bold or italic */

sup.reference {
    font-weight: normal;
    font-style: normal;
}
 
/* Styling for citations */

span.citation, cite {
    font-style: normal;
    word-wrap: break-word;
}
 
/* For linked citation numbers and document IDs, where
the number need not be shown on a screen or a handheld,
but should be included in the printed version
*/

@media screen, handheld {
    span.citation *.printonly {
        display: none;
    }
}

/* Default skin for navigation boxes */

table.navbox {            /* Navbox container style */
    border: 1px solid #7384b5;
    width: 100%;
    margin: auto;
    clear: both;
    font-size: 88%;
    text-align: center;
    padding: 1px;
}

/* Navbox Layout */

table.navbox + table.navbox {  /* Single pixel border between adjacent navboxes */
    margin-top: -1px;          /* (doesn't work for IE6, but that's okay)       */
}

.navbox-title, .navbox-abovebelow, table.navbox th {
    text-align: center;      /* Title and above/below styles */
    padding-left: 1em;
    padding-right: 1em;
}

.navbox-group {              /* Group style */
    white-space: nowrap;
    text-align: right;
    font-weight: bold;
    padding-left: 1em;
    padding-right: 1em;
}

.navbox-list {
    text-align: left;
}

.collapseButton {          /* 'show'/'hide' buttons created dynamically */
    float: right;          /* by the CollapsibleTables javascript in    */
    font-weight: normal;   /* [[MediaWiki:Common.js]]are styled here    */
    text-align: right;     /* so they can be customised.                */
    width: auto;
}

.navbox .collapseButton {  /* In navboxes, the show/hide button balances */
    width: 6em;            /* the vde links from [[Template:Tnavbar]],   */
}                          /* so they need to be the same width.         */

.navbox-title, .navbox-above, .navbox-below {
    padding-left: 1em;
    padding-right: 1em;
    text-align: center;
}

/* Navbox Colors */

.navbox, .navbox-subgroup {
    background: #fdfdfd;     /* Background color */
}

.navbox-list {
    border-color: #fdfdfd;   /* Must match background color */
}

.navbox-title, table.navbox th {
    background: #cedaff;     /* Level 1 color */
}

.navbox-abovebelow, .navbox-group, .navbox-subgroup .navbox-title {
    background: #dde6ff;     /* Level 2 color */
}

.navbox-subgroup .navbox-group, .navbox-subgroup .navbox-abovebelow {
    background: #dde6ff;     /* Level 3 color */
}

.navbox-even {
    background: #f7f7f7;     /* Even row striping */
}

.navbox-odd {
    background: transparent; /* Odd row striping */
}

/* Infobox template style */
.infobox {
    border: 1px solid #aaa;
    background-color: #f9f9f9;
    color: black;
    margin: 0.5em 0 0.5em 1em;
    padding: 0.2em;
    float: right;
    clear: right;
}

.infobox td, .infobox th {
    vertical-align: top;
}

.infobox p {
    margin: 0;
    line-height:1.8;
}

.infobox ul {
    margin-top: 0;
}

.infobox caption {
    font-size: larger;
}

.infobox.bordered {
    border-collapse: collapse;
}

.infobox.bordered td, .infobox.bordered th {
    border: 1px solid #aaa;
}

.infobox.bordered .borderless td, .infobox.bordered .borderless th {
    border: 0;
}
 
.infobox.sisterproject {
    width: 20em;
    font-size: 90%;
}
 
.infobox.standard-talk {
    border: 1px solid #c0c090;
    background-color: #f8eaba;
}

.infobox.standard-talk.bordered td, .infobox.standard-talk.bordered th {
    border: 1px solid #c0c090;
}
 
/* styles for bordered infobox with merged rows */
.infobox.bordered .mergedtoprow td,
.infobox.bordered .mergedtoprow th {
    border: 0;
    border-top: 1px solid #aaa;
    border-right: 1px solid #aaa;
}
 
.infobox.bordered .mergedrow td,
.infobox.bordered .mergedrow th {
    border: 0;
    border-right: 1px solid #aaa;
}
 
/* Normal font styling for table row headers with scope="row" tag */
.wikitable.plainrowheaders th[scope=row] {
    font-weight: normal;
    text-align: left;
}
 
/* lists in data cells are always left-aligned */
.wikitable td ul,
.wikitable td ol,
.wikitable td dl {
    text-align: left;
}
 
/* Makes redirects appear in italics in categories and on [[Special:Allpages]] */
.redirect-in-category, .allpagesredirect {
    font-style: italic;
}
 
/* Icons for medialist templates [[Template:Listen]],
[[Template:Multi-listen_start]], [[Template:Video]],
[[Template:Multi-video_start]]
*/
div.listenlist {
background: url("https://upload.wikimedia.org/wikipedia/commons/3/3f/Gnome_speakernotes_30px.png");
padding-left: 40px;
}
 
/* Style rules for media list templates */
div.medialist {
min-height: 50px;
margin: 1em;
background-position: top left;
background-repeat: no-repeat;
}
div.medialist ul {
list-style-type: none;
list-style-image: none;
margin: 0;
}
div.medialist ul li {
padding-bottom: 0.5em;
}
div.medialist ul li li {
font-size: 91%;
padding-bottom: 0;
}

 
/* Content in columns with CSS instead of tables [[Template:Columns]] */
div.columns-2 div.column {
float: left;
width: 50%;
min-width: 300px;
}
div.columns-3 div.column {
float: left;
width: 33.3%;
min-width: 200px;
}
div.columns-4 div.column {
float: left;
width: 25%;
min-width: 150px;
}
div.columns-5 div.column {
float: left;
width: 20%;
min-width: 120px;
}
 
/* Messagebox templates */
.messagebox {
border: 1px solid #aaa;
background-color: #f9f9f9;
width: 80%;
margin: 0 auto 1em auto;
padding: .2em;
}
.messagebox.merge {
border: 1px solid #c0b8cc;
background-color: #f0e5ff;
text-align: center;
}
.messagebox.cleanup {
border: 1px solid #9f9fff;
background-color: #efefff;
text-align: center;
}
.messagebox.standard-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
margin: 4px auto;
}
/* For old WikiProject banners inside banner shells. */
.mbox-inside .standard-talk,
.messagebox.nested-talk {
border: 1px solid #c0c090;
background-color: #f8eaba;
width: 100%;
margin: 2px 0;
padding: 2px;
}
.messagebox.small {
width: 238px;
font-size: 85%;
float: right;
clear: both;
margin: 0 0 1em 1em;
line-height: 1.25em;
}
.messagebox.small-talk {
width: 238px;
font-size: 85%;
float: right;
clear: both;
margin: 0 0 1em 1em;
line-height: 1.25em;
background: #F8EABA;
}
 
/* Cell sizes for ambox/tmbox/imbox/cmbox/ombox/fmbox/dmbox message boxes */
th.mbox-text, td.mbox-text {   /* The message body cell(s) */
border: none;
padding: 0.25em 0.9em;     /* 0.9em left/right */
width: 100%;               /* Make all mboxes the same width regardless of text length */
}
td.mbox-image {                /* The left image cell */
border: none;
padding: 2px 0 2px 0.9em;  /* 0.9em left, 0px right */
text-align: center;
}
td.mbox-imageright {           /* The right image cell */
border: none;
padding: 2px 0.9em 2px 0;  /* 0px left, 0.9em right */
text-align: center;
}
td.mbox-empty-cell {           /* An empty narrow cell */
border: none;
padding: 0px;
width: 1px;
}
 
/* Article message box styles */
table.ambox {
margin: 0px 10%;                  /* 10% = Will not overlap with other elements */
border: 1px solid #aaa;
border-left: 10px solid #1e90ff;  /* Default "notice" blue */
background: #fbfbfb;
}
table.ambox + table.ambox {      /* Single border between stacked boxes. */
margin-top: -1px;
}
.ambox th.mbox-text,
.ambox td.mbox-text {            /* The message body cell(s) */
padding: 0.25em 0.5em;       /* 0.5em left/right */
}
.ambox td.mbox-image {           /* The left image cell */
padding: 2px 0 2px 0.5em;    /* 0.5em left, 0px right */
}
.ambox td.mbox-imageright {      /* The right image cell */
padding: 2px 0.5em 2px 0;    /* 0px left, 0.5em right */
}
 
table.ambox-notice {
border-left: 10px solid #1e90ff;    /* Blue */
}
table.ambox-speedy {
border-left: 10px solid #b22222;    /* Red */
background: #fee;                   /* Pink */
}
table.ambox-delete {
border-left: 10px solid #b22222;    /* Red */
}
table.ambox-content {
border-left: 10px solid #f28500;    /* Orange */
}
table.ambox-style {
border-left: 10px solid #f4c430;    /* Yellow */
}
table.ambox-move {
border-left: 10px solid #9932cc;    /* Purple */
}
table.ambox-protection {
border-left: 10px solid #bba;       /* Gray-gold */
}
 
/* Image message box styles */
table.imbox {
margin: 4px 10%;
border-collapse: collapse;
border: 3px solid #1e90ff;    /* Default "notice" blue */
background: #fbfbfb;
}
.imbox .mbox-text .imbox {  /* For imboxes inside imbox-text cells. */
margin: 0 -0.5em;       /* 0.9 - 0.5 = 0.4em left/right.        */
display: block;         /* Fix for webkit to force 100% width.  */
}
.mbox-inside .imbox {       /* For imboxes inside other templates.  */
margin: 4px;
}
 
table.imbox-notice {
border: 3px solid #1e90ff;    /* Blue */
}
table.imbox-speedy {
border: 3px solid #b22222;    /* Red */
background: #fee;             /* Pink */
}
table.imbox-delete {
border: 3px solid #b22222;    /* Red */
}
table.imbox-content {
border: 3px solid #f28500;    /* Orange */
}
table.imbox-style {
border: 3px solid #f4c430;    /* Yellow */
}
table.imbox-move {
border: 3px solid #9932cc;    /* Purple */
}
table.imbox-protection {
border: 3px solid #bba;       /* Gray-gold */
}
table.imbox-license {
border: 3px solid #88a;       /* Dark gray */
background: #f7f8ff;          /* Light gray */
}
table.imbox-featured {
border: 3px solid #cba135;    /* Brown-gold */
}
 
/* Category message box styles */
table.cmbox {
margin: 3px 10%;
border-collapse: collapse;
border: 1px solid #aaa;
background: #DFE8FF;    /* Default "notice" blue */
}
 
table.cmbox-notice {
background: #D8E8FF;    /* Blue */
}
table.cmbox-speedy {
margin-top: 4px;
margin-bottom: 4px;
border: 4px solid #b22222;    /* Red */
background: #FFDBDB;          /* Pink */
}
table.cmbox-delete {
background: #FFDBDB;    /* Red */
}
table.cmbox-content {
background: #FFE7CE;    /* Orange */
}
table.cmbox-style {
background: #FFF9DB;    /* Yellow */
}
table.cmbox-move {
background: #E4D8FF;    /* Purple */
}
table.cmbox-protection {
background: #EFEFE1;    /* Gray-gold */
}
 
/* Other pages message box styles */
table.ombox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #aaa;       /* Default "notice" gray */
background: #f9f9f9;
}
 
table.ombox-notice {
border: 1px solid #aaa;       /* Gray */
}
table.ombox-speedy {
border: 2px solid #b22222;    /* Red */
background: #fee;             /* Pink */
}
table.ombox-delete {
border: 2px solid #b22222;    /* Red */
}
table.ombox-content {
border: 1px solid #f28500;    /* Orange */
}
table.ombox-style {
border: 1px solid #f4c430;    /* Yellow */
}
table.ombox-move {
border: 1px solid #9932cc;    /* Purple */
}
table.ombox-protection {
border: 2px solid #bba;       /* Gray-gold */
}
 
/* Talk page message box styles */
table.tmbox {
margin: 4px 10%;
border-collapse: collapse;
border: 1px solid #c0c090;    /* Default "notice" gray-brown */
background: #f8eaba;
}
.mediawiki .mbox-inside .tmbox { /* For tmboxes inside other templates. The "mediawiki" class ensures that */
margin: 2px 0;               /* this declaration overrides other styles (including mbox-small above)   */
width: 100%;                 /* For Safari and Opera */
}
.mbox-inside .tmbox.mbox-small { /* "small" tmboxes should not be small when  */
line-height: 1.5em;          /* also "nested", so reset styles that are   */
font-size: 100%;             /* set in "mbox-small" above.                */
}
 
table.tmbox-speedy {
border: 2px solid #b22222;    /* Red */
background: #fee;             /* Pink */
}
table.tmbox-delete {
border: 2px solid #b22222;    /* Red */
}
table.tmbox-content {
border: 2px solid #f28500;    /* Orange */
}
table.tmbox-style {
border: 2px solid #f4c430;    /* Yellow */
}
table.tmbox-move {
border: 2px solid #9932cc;    /* Purple */
}
table.tmbox-protection,
table.tmbox-notice {
border: 1px solid #c0c090;    /* Gray-brown */
}
 
/* Disambig and set index box styles */
table.dmbox {
clear: both;
margin: 0.9em 1em;
border-top: 1px solid #ccc;
border-bottom: 1px solid #ccc;
background: transparent;
}
 
/* Footer and header message box styles */
table.fmbox {
clear: both;
margin: 0.2em 0;
width: 100%;
border: 1px solid #aaa;
background: #f9f9f9;     /* Default "system" gray */
}
table.fmbox-system {
background: #f9f9f9;
}
table.fmbox-warning {
border: 1px solid #bb7070;  /* Dark pink */
background: #ffdbdb;        /* Pink */
}
table.fmbox-editnotice {
background: transparent;
}
/* Div based "warning" style fmbox messages. */
div.mw-warning-with-logexcerpt,
div.mw-lag-warn-high,
div.mw-cascadeprotectedwarning,
div#mw-protect-cascadeon {
clear: both;
margin: 0.2em 0;
border: 1px solid #bb7070;
background: #ffdbdb;
padding: 0.25em 0.9em;
}
/* Div based "system" style fmbox messages.
Used in [[MediaWiki:Readonly lag]]. */
div.mw-lag-warn-normal,
div.fmbox-system {
clear: both;
margin: 0.2em 0;
border: 1px solid #aaa;
background: #f9f9f9;
padding: 0.25em 0.9em;
}
 
/* These mbox-small classes must be placed after all other
ambox/tmbox/ombox etc classes. "body.mediawiki" is so
they override "table.ambox + table.ambox" above. */
body.mediawiki table.mbox-small {   /* For the "small=yes" option. */
clear: right;
float: right;
margin: 4px 0 4px 1em;
width: 238px;
font-size: 88%;
line-height: 1.25em;
}
body.mediawiki table.mbox-small-left {   /* For the "small=left" option. */
margin: 4px 1em 4px 0;
width: 238px;
border-collapse: collapse;
font-size: 88%;
line-height: 1.25em;
}
 
 
/* Remove default styles for [[MediaWiki:Noarticletext]]. */
div.noarticletext {
border: none;
background: transparent;
padding: 0;
}
 
#wpSave {
font-weight: bold;
}
 
/* class hiddenStructure is defunct. See [[Wikipedia:hiddenStructure]] */
.hiddenStructure {
display: inline ! important;
color: #f00;
background-color: #0f0;
}
 
/* suppress missing interwiki image links where #ifexist cannot
be used due to high number of requests see .hidden-redlink on
http://meta.wikimedia.org/wiki/MediaWiki:Common.css
*/
.check-icon a.new {
display: none;
speak: none;
}
 
/* Removes underlines from certain links */
.nounderlines a,
.IPA a:link, .IPA a:visited {
text-decoration: none;
}
 
/* Standard Navigationsleisten, aka box hiding thingy
from .de.  Documentation at [[Wikipedia:NavFrame]]. */
div.NavFrame {
margin: 0;
padding: 4px;
border: 1px solid #aaa;
text-align: center;
border-collapse: collapse;
font-size: 95%;
}
div.NavFrame + div.NavFrame {
border-top-style: none;
border-top-style: hidden;
}
div.NavPic {
background-color: #fff;
margin: 0;
padding: 2px;
float: left;
}
div.NavFrame div.NavHead {
height: 1.6em;
font-weight: bold;
background-color: #ccf;
position: relative;
}
div.NavFrame p,
div.NavFrame div.NavContent,
div.NavFrame div.NavContent p {
font-size: 100%;
}
div.NavEnd {
margin: 0;
padding: 0;
line-height: 1px;
clear: both;
}
a.NavToggle {
position: absolute;
top: 0;
right: 3px;
font-weight: normal;
font-size: 90%;
}
 
/* Hatnotes and disambiguation notices */
.rellink,
.dablink {
font-style: italic;
padding-left: 2em;
margin-bottom: 0.5em;
}
.rellink i,
.dablink i {
font-style: normal;
}
 
/* Style for horizontal UL lists */
.horizontal ul {
padding: 0;
margin: 0;
}
.horizontal li {
padding: 0 0.6em 0 0.4em;
display: inline;
border-right: 1px solid;
}
.horizontal li:last-child {
border-right: none;
padding-right: 0;
}
 
/* Allow transcluded pages to display in lists rather than a table.
Compatible in Firefox; incompatible in IE6. */
.listify td    { display: list-item; }
.listify tr    { display: block; }
.listify table { display: block; }
 
/* Geographical coordinates defaults. See [[Template:Coord/link]]
for how these are used. The classes "geo", "longitude", and
"latitude" are used by the [[Geo microformat]].
*/
.geo-default, .geo-dms, .geo-dec  { display: inline; }
.geo-nondefault, .geo-multi-punct { display: none; }
.longitude, .latitude             { white-space: nowrap; }
 
/* When &lt;div class="nonumtoc"&gt; is used on the table of contents,
the ToC will display without numbers */
.nonumtoc .tocnumber { display: none; }
.nonumtoc #toc ul,
.nonumtoc .toc ul {
line-height: 1.5em;
list-style: none;
margin: .3em 0 0;
padding: 0;
}
.nonumtoc #toc ul ul,
.nonumtoc .toc ul ul {
margin: 0 0 0 2em;
}
 
/* Allow limiting of which header levels are shown in a TOC;
&lt;div class="toclimit-3"&gt;, for instance, will limit to
showing ==headings== and ===headings=== but no further
(as long as there are no =headings= on the page, which
there shouldn't be according to the MoS).
*/
.toclimit-2 .toclevel-1 ul,
.toclimit-3 .toclevel-2 ul,
.toclimit-4 .toclevel-3 ul,
.toclimit-5 .toclevel-4 ul,
.toclimit-6 .toclevel-5 ul,
.toclimit-7 .toclevel-6 ul {
display: none;
}
 
/* Styling for Template:Quote */
blockquote.templatequote {
margin-top: 0;
}
blockquote.templatequote div.templatequotecite {
line-height: 1em;
text-align: left;
padding-left: 2em;
margin-top: 0;
}
blockquote.templatequote div.templatequotecite cite {
font-size: 85%;
}
 
/* User block messages */
div.user-block {
padding: 5px;
margin-bottom: 0.5em;
border: 1px solid #A9A9A9;
background-color: #FFEFD5;
}
 
/* Prevent line breaks in silly places:
1) Links when we don't want them to
2) Bold "links" to the page itself
2) HTML formulae
3) Ref tags with group names &lt;ref group="Note"&gt; --&gt; "[Note 1]"
*/
.nowraplinks a,
.nowraplinks .selflink,
span.texhtml,
sup.reference a {
white-space: nowrap;
}
 
/* For template documentation */
.template-documentation {
clear: both;
margin: 1em 0 0 0;
border: 1px solid #aaa;
background-color: #ecfcf4;
padding: 1em;
}
 
/* Inline divs in ImageMaps (code borrowed from de.wiki) */
.imagemap-inline div {
display: inline;
}
 
/* Increase the height of the image upload box */
#wpUploadDescription {
height: 13em;
}
 
/* Reduce line-height for &lt;sup&gt; and &lt;sub&gt; */
sup, sub {
line-height: 1em;
}
 
/* Minimum thumb width */
.thumbinner {
min-width: 100px;
}
 
/* Remove white border from thumbnails */
div.thumb {
border: none;
}
div.tright {
border: none;
margin: 0.5em 0 0.8em 1.4em;
}
div.tleft {
border: none;
margin: 0.5em 1.4em 0.8em 0;
}
 
/* Makes the background of a framed image white instead of gray. */
/* Only visible with transparent images. */
div.thumb img.thumbimage {
background-color: #fff;
}
 
/* The backgrounds for galleries. */
#content .gallerybox div.thumb {
background-color: #F9F9F9;   /* Light gray padding */
}
/* Put a chequered background behind images, only visible if they have transparency */
/*.gallerybox .thumb img,
#file img {
background: white url("https://upload.wikimedia.org/wikipedia/commons/5/5d/Checker-16x16.png") repeat;
}*/
/* But not on articles, user pages, portals or with opt-out. */
.ns-0 .gallerybox .thumb img,
.ns-2 .gallerybox .thumb img,
.ns-100 .gallerybox .thumb img,
.nochecker .gallerybox .thumb img {
background: white;
}
 
/* Prevent floating boxes from overlapping any category listings,
file histories, edit previews, and edit [Show changes] views */
#mw-subcategories, #mw-pages, #mw-category-media,
#filehistory, #wikiPreview, #wikiDiff {
clear: both;
}
 
/* Selectively hide headers in WikiProject banners */
.wpb .wpb-header             { display: none; }
.wpbs-inner .wpb .wpb-header { display: block; }     /* for IE */
.wpbs-inner .wpb .wpb-header { display: table-row; } /* for real browsers */
.wpbs-inner .wpb-outside     { display: none; }      /* hide things that should only display outside shells */
 
/* Styling for Abuse Filter tags */
.mw-tag-markers {
font-family:sans-serif;
font-style:italic;
font-size:90%;
}
 
/* Fix so &lt;tt&gt;, &lt;code&gt; and &lt;pre&gt; tags get normal text size also in
some versions of Firefox, Safari, Konqueror, Chrome etc.
Remove once r69336 and r76322 are live. */
tt, code, pre, kbd, samp {
font-family: monospace, "Courier New";
}
/* Same fix, but for inline code generated by #tag:syntaxhighlight */
span.mw-geshi {
font-family: monospace, "Courier New" !important;
}
 
/* Remove bullets when there are multiple edit page warnings */
ul.permissions-errors &gt; li {
list-style: none;
}
ul.permissions-errors {
margin: 0;
}
 
/* No linewrap on the labels of the login/signup page */
body.page-Special_UserLogin .mw-label label,
body.page-Special_UserLogin_signup .mw-label label { white-space : nowrap; }
 
/* Fix an alignment issue with oggplayer when rendered as center */
.center .ogg-player-options ul {
margin: 0.3em 0px 0px 1.5em;
}
 
/* &lt;/source&gt; */

/* Experimental CSS-based Ruby markup support */
/* Ruby text*/

ruby {
	ruby-align: space-around;
    display: inline-table;
    text-align: center;
    border-collapse: collapse;
/* border collapse mechanism will be used to adjust vertical alignment */
    vertical-align: bottom;
/* if ruby text contains text only and there are two ruby annotations (one placed above the base and one below) 
then vertical centering roughly aligns baseline of base with baseline of parent */
    /* border-bottom: solid 1.1em transparent; */
/* o.75em is height of ruby text (0.5000d7 1.2em = 0.6em) plus space between baseline and text-bottom (about 0.15em) 
this extra border is counter-weight used to restore vertical centering broken by presence of ruby text (in case if 
there is only one ruby annotation, if there are two annotations then counter-weight is no longer necessary and can 
be annihilated using border collapse mechanism) */
}

rt {
	text-align: center;
}
/* 'ruby { text-align: center; } does not cascade to rt now */

ruby &gt; rt, rtc {
    display: table-header-group;
}
/* used to move first ruby container above the base */

/* ruby &gt; rb, rbc, ruby &gt; rt + rt, rtc + rtc {
    display: table-row;
} */
/* base and second ruby are formatted as table-rows */

ruby &gt; rt + rt, rtc + rtc {
    border-bottom: hidden;
}
/* if there are two annotations then extra border is no longer necessary and can be annihilated using border collapse mechanism */

rb, rbc, rt, rtc {
    white-space: nowrap;
}
/* prohibits line breaks inside ruby text */

rtc &gt; rt, rbc &gt; rb {
    display: table-cell;
}
/* used to distribute annotations in table like manner */

rtc &gt; rt[rbspan] {
    column-span: all;
}
/* ruby text may span several cells */

ruby &gt; rt, rtc {
    font-size: 0.85em;
    line-height: 1.2em;
    letter-spacing: -0.1em;
    font-family: "Consolas", "Inconsolata", monospace;
}
/* font-size of ruby text is reduced */

rp {
    display: none;
}
/* fallback markup is no longer necessary */


/* For [[Template:Lyrics]] */

.template_lyrics {
}
.template_lyrics td, .template_lyrics th {
    padding: 5px;
}
.template_lyrics table td, .template_lyrics table th {
    /* don't pad inner tables, if they exist */
    padding: 0px;
}
.template_lyrics th {
    font-size: 120%; 
}
.template_lyrics .lyrics_row td p {
    white-space: pre-line;
}

/* Cell Styles */
/* outcell:  dark-blue outer border of table
   incell:  light-blue table cells with various rounded corners */

.outcell {
    border: 1px solid #7384B5;
    border-radius: 5px;
}
.incell, .incell_top, .incell_bottom, .incell_topleft, 
.incell_topright, .incell_bottomleft, .incell_bottomright {
    background: #DDE6FF;
    text-align: center;
    font-size: 120%;
}
.incell_top {
    border-radius: 3px 3px 0px 0px;
}
.incell_bottom {
    border-radius: 0px 0px 3px 3px;
}
.incell_topleft {
    border-radius: 3px 0px 0px 0px;
}
.incell_topright {
    border-radius: 0px 3px 0px 0px;
}
.incell_bottomleft {
    border-radius: 0px 0px 0px 3px;
}
.incell_bottomright {
    border-radius: 0px 0px 3px 0px;
}

/* Darkslime's header image */
/* 1.23 change: added .mw-headline class to match new HTML structure */
/* Moved to "before" pseudo-element for easier styling */
.mw-headline::before {
   content: url('images/yinyangz.png');
   margin-right: 5px;
}
/* 1.23 change: properly position section headers that contain just an external link */
.mw-headline&gt;a.external {
  padding-left: 22px;
}
#toc h2, .toc h2 {
  background-image: none;
}
h1, h2 {
  border-bottom-color: #7384B5;
}
.catlinks, .toc, #toc, .mw-warning, div#simpleSearch {
  border-color: #7384B5;
}

/* Ensure everything inside a spoiler is blacked out. Without this, links show through. */
.t_hidetext, .t_hidetext * {
  background-color: black;
  color: black;
}
.t_hidetext a {
  color: black !important;
}
.t_hidetext:hover, .t_hidetext:hover *, .t_hidetext:focus, .t_hidetext:focus * {
  color: white !important;
}
.t_hidetext:hover a {
  color: #30A0EF !important;
}
.t_hidetext:hover a:visited {
  color: #7084DA !important;
}
.t_hidetext:hover a.new {
  color: #ED6A6A !important;
}
.t_hidetext:hover a.new:visited {
  color: #ED9999 !important;
}
.t_hidetext:hover a.extiw {
  color: #47C !important;
}
.t_hidetext:hover a.extiw:visited {
  color: #969 !important;
}

/* Force pre tag auto wrap text */
pre {
    white-space: pre-wrap;
}

/* Make Lua text readable */
.source-lua {
    font-size: 1.2em;
}

/* Used for [[User:K/de:Filename_Conflicts]] */
.de-image&gt;a {
  background: none !important;
}
.de-image&gt;a&gt;img {
  width: 200px;
}

/* Touhou Wiki Main Page mkIII -- Credit: CSS by Darkslime, Sefam, K; Artwork by Leo Modesto */
/* Portability notes: Uses .incell_top, so also copy style rules using that. */
#MainPage {
	width: 100%;
	padding: 1px 3px 1px 3px;
	box-sizing: border-box;
}
#MainPage * {
	box-sizing: border-box;
}

#mp-LeftColumn {
	float: left;
	width: 74.8%;
	margin-right: 0.1%;
}
#mp-RightColumn {
	float: right;
	width: 24.8%;
	margin-left: 0.1%;
}

.mp-box {
	float: left;
}
.mp-innerBox {
	position: relative;
	width: 100%;
	border: 1px solid #7384B5;
	border-radius: 5px 5px 5px 5px;
	margin: 3px 1px;
}
.mp-innerBox&gt;div {
	margin: 6px;
}

.mp-box.mp-wide {
	width: 100%;
}
.mp-wide&gt;.mp-tall {
	width: 33%;
	padding: 0 3px;
}
.mp-tall&gt;.mp-innerBox {
	width: 100%;
	min-height: 775px;
	max-height: 1495px;
}

#mp-Games {
	padding-left: 0;
}
#mp-Music {
}
#mp-PrintWorks {
	width: 34%;
	padding-right: 0;
}

#mp-Games&gt;.mp-innerBox {
	background-color: #FFF4EE;
    border-color: #A88580;
}
#mp-Music&gt;.mp-innerBox {
	background-color: #FFFBEE;
    border-color: #A8A077;
}
#mp-PrintWorks&gt;.mp-innerBox {
	background-color: #F4F9FF;
    border-color: #9298A8;
}

#BoxOthers&gt;.mp-innerBox {
	clear: left;
	padding-top: 5px;
	width: 100%;
}

.mp-innerBox&gt;.mp-header {
	text-align: center;
	padding: 2px;
	font-size: 120%;
	border-radius: 3px 3px 0px 0px;
}

#mp-Games .mp-header {
	background-color: #FFC9C2;
}
#mp-Music .mp-header {
	background-color: #FFF3B4;
}
#mpPrintWorks .mp-header {
	background-color: #C4D3FF;
}

.mp-subBox {
	margin-top: 5px;
	float: none;
	clear: both;
}
#mp-Info {
	width: 100%;
}
#mp-Info .mp-content {
	margin-top: 0.25em;
	margin-bottom: 0.75em;
}

/* Images by leomodesto */
.mp-innerBox&gt;.mp-image {
        margin: 0;
        position: absolute;
        right: 0;
}

/* Cirno-Daiyousei (Header) */
#mp-Welcome .mp-image {
    top: -69px;
    right: 0px;
    width: 152px;
    height: 80px;
    position: absolute;
    background: transparent url("skins/common/images/charsprites.png") 0px 0px no-repeat;
}
#mp-Welcome .mp-image:hover {
    background-position: -152px 0px;
}

/* Lily White (News) */
#mp-News .mp-image {
        width: 103px;
        height: 93px;
        right: -10px;
        top: -27px;
        background: transparent url("skins/common/images/charsprites.png") -201px -81px no-repeat;
}
#mp-News .mp-image.mp-smaller-image {
        background: transparent url("skins/common/images/charsprites.png") -151px -164px no-repeat;
        width: 74px;
        height: 70px;
        right: -6px;
}

/* Three Fairies (Body columns, full- and low-resolution) */
#mp-WorksColumns .mp-image {
        right: 0px;
        height: 82px;
}
#mp-Games .mp-image {
        background: transparent url("skins/common/images/charsprites.png") 0px -81px no-repeat;
        top: -12px;
        width: 60px;
} 
#mp-Music .mp-image {
        background: transparent url("skins/common/images/charsprites.png") -61px -81px no-repeat;
        top: -14px;
        width: 68px;
}
#mp-PrintWorks .mp-image {
        background: transparent url("skins/common/images/charsprites.png") -130px -81px no-repeat;
        top: -20px;
        width: 70px;
}
#mp-WorksColumns .mp-image.mp-smaller-image {
        right: 0px;
        top: -12px;
        height: 60px;
}
#mp-Games .mp-image.mp-smaller-image {
        background: transparent url("skins/common/images/charsprites.png") 0px -164px no-repeat;
        width: 45px;
}
#mp-Music .mp-image.mp-smaller-image {
        background: transparent url("skins/common/images/charsprites.png") -45px -164px no-repeat;
        width: 51px;
}
#mp-PrintWorks .mp-image.mp-smaller-image {
        background: transparent url("skins/common/images/charsprites.png") -98px -164px no-repeat;
        width: 52px;
}

/* --- end main page mkIII */

/* For positioning icons at top-right, used in Template
   "Spoken Article" and "Featured Article" */
div.topicon {
  position: absolute;
  top: -2em;
  margin-right: -10px;
  display: block !important;
}

/* To make CategoryTree listings resemble their big brother a bit more. */
.CategoryTreeLabelPage {
  font-style: normal;
}

.CategoryTreeTag {
  column-count: 3;
}

/* Community Portal items */
.PortalNewsOuter {
    background: #ffffff;
    width: 100%;
    text-align: center;
    border-radius: 80px; 
    border: 10px solid #dbf8ce;
}
.PortalNewsInner {
    background: #b5dbc1;
    width: 45%;
    border-radius: 80px;
    font-size: 200%;
    color: #285c4d;
}
.NewsBox {
    width: 30%;   
    border-radius: 20px;
    border: 3px solid;
    padding: 10px;
}
.RoundyLabel {
    width:20%;
    border-top-right-radius: 15px;
    border-bottom-right-radius: 15px;
    border: 1px solid;
}

/* Things that should be visible to sysops and accountcreators by default */
.sysop-show, .accountcreator-show {
    display: none;
}

/* Fix for userpage fairies - since MW 1.22 most styles are stripped from DISPLAYTITLE */

.user-fairy-pre {
    display: block;
    width: 96%;
    height: 50px;
}

.user-fairy-container {
    display: block;
    position: relative;
    right: 0;
    bottom: 0;
}

.user-fairy-image {
    display: block;
    height: 83px;
    right: 0px;
    bottom: 3px;
    position: absolute;
    top: -69px;
    width: 152px;
    background: transparent url("skins/common/images/charsprites.png") 0px 0px no-repeat;
}

.user-fairy-cirno &gt; * &gt; .user-fairy-image:hover {
    background-position: -152px 0px;
}

.user-fairy-lily &gt; .user-fairy-pre {
    height: 71px;
}

.user-fairy-lily &gt; * &gt; .user-fairy-image {
    top: -90px;
    width: 103px;
    height: 93px;
    background-position: -201px -81px;
}

.user-fairy-sunny &gt; .user-fairy-pre {
    height: 46px;
}

.user-fairy-sunny &gt; * &gt; .user-fairy-image {
    top: -65px;
    width: 60px;
    height: 83px;
    background-position: 0px -81px;
}

.user-fairy-star &gt; .user-fairy-pre {
    height: 57px;
}

.user-fairy-star &gt; * &gt; .user-fairy-image {
    top: -76px;
    width: 70px;
    height: 83px;
    background-position: -129px -81px;
}

.user-fairy-luna &gt; * &gt; .user-fairy-image {
    top: -69px;
    width: 68px;
    height: 83px;
    background-position: -60px -81px;
}

/* Sitenotice AutoScroll CSS */
#scrollDiv {
    width: 100%;
    height: 25px;
    line-height: 25px;
    overflow: hidden;
}

#scrollDiv li {
    height: 25px;
    padding-left: 10px;
    list-style: none;
}

/* Custom tab */

/* Tab image */
.tab_content_container {
    text-align: center;
    margin: 0;
    padding: 0;
    display: inline-block;
}
.tab_content_button {
    display: inline-block;
    padding: 2px;
    margin-left: 2px;
    margin-right: 2px;
    background-color: #eee;
    text-align: center;
    box-shadow: 0 0 3px 0 #000;
    cursor: pointer;
}

.tab_content_content {
    padding: 2px;
    border: 1px solid black;
    padding: 3px;
    display: none;
}

/* Spell Card Info use */

.scwrapper {
    width: 800px;
    display: grid;
    grid-template-columns: auto 1fr;
    margin: 1em;
    border-radius: 8px;
    border: 1px solid #4d7cff;
}

.scimage {
    border: 0;
    padding: 5px;
}

div.scimage img {
    border-radius: 8px;
}

.scinfo {
    display: grid;
    grid-template-columns: 2fr 7fr;
}

.sclabel {
    font-weight: bold;
    text-align: right;
    padding: 5px;
    white-space: nowrap;
}

.sccontent {
    padding: 5px;
}

.sclabeltext {
    border-radius: 8px;
    border: 1px solid none;
    background-color: #4d7cff;
    color: #ffffff;
    padding: 5px;
}

/* Overall High Score Board use */

.txtcenter {
    text-align: center;
}

table.highscorewrapper {
    border-style: none;
    padding: 0;
    width: 100%;
}

.highscorecol {
    border-radius: 8px;
}

.highscoretitle {
    background-color: #ff3333;
    color: #ffffff;
}

.highscoretitlealt {
    border-color: #ff3333;
    border-style: solid;
    border-width: 1px;
    background-color: transparent;
    color: #000000;
}

.highscoreentry {
    border-style: solid;
    border-width: 1px;
    border-radius: 8px;
}

.highscoreth6bk {
    border-color: #990000;
    background-color: #990000;
    color: #ffffff;
}

.highscorenum {
    text-align: right;
    padding-right: 10px;
}

.highscoreth06bk {
    border-color: #990000;
    background-color: #990000;
    color: #ffffff;
}

.highscoreth06 {
    border-color: #990000;
}

.highscoreth07bk {
    border-color: #ff8ed2;
    background-color: #ff8ed2;
    color: #ffffff;
}

.highscoreth07 {
    border-color: #ff8ed2;
}

.highscoreth08bk {
    border-color: #333399;
    background-color: #333399;
    color: #ffffff;
}

.highscoreth08 {
    border-color: #333399;
}

.highscoreth10bk {
    border-color: #96b300;
    background-color: #96b300;
    color: #ffffff;
}

.highscoreth10 {
    border-color: #96b300;
}

.highscoreth11bk {
    border-color: #591400;
    background-color: #591400;
    color: #ffffff;
}

.highscoreth11 {
    border-color: #591400;
}

.highscoreth12bk {
    border-color: #4169e1;
    background-color: #4169e1;
    color: #ffffff;
}

.highscoreth12 {
    border-color: #4169e1;
}

.highscoreth128bk {
    border-color: #00c8c8;
    background-color: #00c8c8;
    color: #ffffff;
}

.highscoreth128 {
    border-color: #00c8c8;
}

.highscoreth13bk {
    border-color: #4a808c;
    background-color: #4a808c;
    color: #ffffff;
}

.highscoreth13 {
    border-color: #4a808c;
}

.highscoreth14bk {
    border-color: #aa7777;
    background-color: #aa7777;
    color: #ffffff;
}

.highscoreth14 {
    border-color: #aa7777;
}

.highscoreth15bk {
    border-color: #6a47be;
    background-color: #6a47be;
    color: #ffffff;
}

.highscoreth15 {
    border-color: #6a47be;
}

.highscoreth16bk {
    border-color: #176e0e;
    background-color: #176e0e;
    color: #ffffff;
}

.highscoreth16 {
    border-color: #176e0e;
}

.highscoreth17bk {
    border-color: #190e0e;
    background-color: #190e0e;
    color: #ffffff;
}

.highscoreth17 {
    border-color: #190e0e;
}

/* Normal Scoreboard use */

.th00dark {
    background-color: #eaecf0;
}

.th06dark {
    background-color: #990000; color: #ffffff;
}

.th07dark {
    background-color: #ff8ed2; color: #ffffff;
}

.th08dark {
    background-color: #333399; color: #ffffff;
}

.th10dark {
    background-color: #96b300; color: #ffffff;
}

.th11dark {
    background-color: #591400; color: #ffffff;
}

.th12dark {
    background-color: #4169e1; color: #ffffff;
}

.th128dark {
    background-color: #00c8c8; color: #ffffff;
}

.th13dark {
    background-color: #4a808c; color: #ffffff;
}

.th14dark {
    background-color: #aa7777; color: #ffffff;
}

.th15dark {
    background-color: #6a47be; color: #ffffff;
}

.th16dark {
    background-color: #176e0e; color: #ffffff;
}

.th17dark {
	background-color: #190e0e; color: #ffffff;
}

.th00border {
    border-color: #f9f9f9;
    border-style: solid;
    border-width: 1px;
}

.th06border {
    border-color: #ff9999;
    border-style: solid;
    border-width: 1px;
}

.th07border {
    border-color: #ffcceb;
    border-style: solid;
    border-width: 1px;
}

.th08border {
    border-color: #8c8cd9;
    border-style: solid;
    border-width: 1px;
}

.th10border {
    border-color: #d9ff1a;
    border-style: solid;
    border-width: 1px;
}

.th11border {
    border-color: #ff6133;
    border-style: solid;
    border-width: 1px;
}

.th12border {
    border-color: #7a96eb;
    border-style: solid;
    border-width: 1px;
}

.th128border {
    border-color: #00e5e6;
    border-style: solid;
    border-width: 1px;
}

.th13border {
    border-color: #8ab7c1;
    border-style: solid;
    border-width: 1px;
}

.th14border {
    border-color: #c4a1a1;
    border-style: solid;
    border-width: 1px;
}

.th15border {
    border-color: #b2a0de;
    border-style: solid;
    border-width: 1px;
}

.th16border {
    border-color: #6fea61;
    border-style: solid;
    border-width: 1px;
}

.th17border {
	border-color: #ac6c6c;
	border-style: solid;
	border-width: 1px;
}

/*Nodesktop class for {{tab content}}*/
.nodesktop {
   display:none;
}

/*h:title implementation for touchscreens*/
/*Touchscreen styles*/
@media(pointer:coarse) {
	/*Container and text relative to enable stacking*/
	span.h\3Atitle_container {
		position:relative;
	}
	/*Start at 0*/
	span.h\3Atitle {
		position:relative;
		z-index:0;
	}
	/*On hover increase to 1 to display above other instances*/
	span.h\3Atitle:hover {
		z-index:1;
	}
	/*tooltip styles*/
	span.h\3Atitle:hover::before {
		content:attr(title);
		position:absolute;
		top:100%;
		width:100%;
		text-align:center;
		color:white;
		background-color:black;
		border:solid 1px white;
		border-radius:5px;
		font-size:75%;
	}
	/*Empty overlay element; hidden at -1 by default*/
	span.h\3Atitle_shield {
		position:absolute;
		left:0;
		top:0;
		z-index:-1;
		width:100%;
		height:100%;
	}
	/*When previous sibling (the text) has hover, moves above it to tank hover from the 2nd tap*/
	span.h\3Atitle:hover+span.h\3Atitle_shield {
		z-index:999;
	}
}
/*Mouse styles*/
@media(pointer:fine){
	span.h\3Atitle_shield {
	display:none;
	}
}</text>
    <sha1>653cd4f19f087cd54a1d4510e5301a67c05af3eb</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>MIPSPro</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>5</id>
    <timestamp>2025-02-04T19:26:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13203" xml:space="preserve">MIPSPro is the IRIX-native C/C++/FORTRAN compiler that was distributed by SGI for use in IRIX development.

This page serves to document MIPSPro's behavior, characteristics, compatibility, and differences from other UNIX-style cc compilers and the GNU Compiler Collection.

For legacy MIPSPro releases and documentation, there will be an IRIX IDO page covering IDO and legacy MIPSPro releases in the future!

=== General ===
MIPSPro is not installed in a standard IRIX install and requires a collection of other discs that contain the compiler, development libraries/header files, toolchain and supporting utilities.

MIPSPro supports three ABIs, O32, N32 and N64 (Not to be confused with the Nintendo 64). The O32 ABI is the MIPSII 32-bit ABI, and stands for Old 32. The N32 ABI is analogous to the Intel x32 ABI used on x64 systems to provide enhancements to 32-bit programs through using 32-bit pointers while offering many of the N64 ABI enhancements over O32. The N64 ABI is the native 64-bit ABI for IRIX.

Several compiler front ends were available, including the C, C++ and FORTRAN compilers. Others may have possibly been available at various points historically.

=== Optimization ===
MIPSPro supports -O0,1,2,3, and fast flags, as well as a number of other optimization/architecture flags:

-mips4 will enable the MIPS IV instruction set

-TARG will enable platform or CPU-specific optimizations

-OPT can tune various optimizations

For a full list, please check: &lt;nowiki&gt;https://irix7.com/techpubs/007-2360-006.pdf&lt;/nowiki&gt;

==== TARG flag ====
The TARG flag controls both platform and CPU specific optimizations and will take a variety of commands:

-TARG:proc=R10000 will, combined with the MIPSIV flag, compile for MIPS IV platforms and enable specific optimizations for the R10000 processors. The resulting binary will run on R5000 and R8000 systems, but will skip the optimizations for those platforms.

-TARG:platform=IP30 will, combined with other flags, enable Octane specific optimizations.

The two commands can be combined as so: -TARG:platform=IP30:proc=R10000 as well as other commands.

==== OPT flag ====
This has a number of useful flags for more carefully optimizing code.

-OPT:space Optimizes the program for size, similar to the GCC -Os flag

-OPT:Olimit=n This sets a cutoff limit on procedure sizes to optimize. Procedures above the set size will be left alone. The compiler will normally during compilation throw notices out advising of potential ways to tune this.

-OPT:alias=value The compilers must normally be very conservative in optimization of memory references involving pointers (especially in C), since aliases (that is, different ways of accessing the same memory) may be very hard to detect. This option may be used to specify that the program being compiled avoids aliasing in various ways. See the above document for various applications.

Other flags are listed in the above document

=== C Programming with MIPSPro ===
Much like GCC and other modern compilers, MIPSPro can be called from the commandline like so:

&lt;code&gt;% cc foo.c&lt;/code&gt;

Where foo.c is a presumably simple test file.

MIPSPro's ABI, compiling and configuration is via &lt;code&gt;/etc/compiler.defaults&lt;/code&gt;. This can be overridden with compile-time flags, or ENV variables. SGI_ABI, for instance, controls the active ABI:

&lt;code&gt;% setenv SGI_ABI -n32&lt;/code&gt;

This will set it to -n32 mode.

==== Strictness ====
MIPSPro is far more strict than GCC about accepting standard C code and its compiler infrastructure is entirely different. Common bad programming techniques that work in GCC may not work on MIPSPro, this section aims to document common pitfalls:

=====Variable Attributes=====

These are not supported, so they have to be patched with #ifdef or removed:

&lt;code&gt;__attribute__(( XXX ))&lt;/code&gt;

This is the structure of these.

One variable attribute can be rewritten to work with MIPSPro: the attribute 'packed' for a struct can be enforced in MIPSPro by placing the struct between two pragma blocks:

&lt;pre&gt;#if defined (__sgi)

+#pragma pack(1)

+#endif

struct {

...

};

&lt;nowiki&gt;#&lt;/nowiki&gt;if defined (__sgi)

+#pragma pack(0)
+#endif
&lt;/pre&gt;

=====Zero Length Arrays=====

This is a GNU extension prior to c99. Using c99 or -c99 flag for cc should allow it to work.

=====Variable Length Arrays=====

Only supported using the c99 driver or -c99.

=====String Literals=====

IRIXNet staff Dexter1 helpfully pointed this out in a forum post:

Shorthand initialization of char a[] = " "; with MIPSpro will go wrong with leading zero bytes. Rewrite that code.

What follows is his example copied mostly-verbatim:
&lt;pre&gt;
&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;stdio.h&gt;

&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;stdlib.h&gt;

&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;memory.h&gt;

int main(void) {

const char a[] = "\0This is a text";

const char b[] = { 0x0, 'T', 'h', 'i', 's', ' ', 'i', 's', ' ', 'a',

' ', 't', 'e', 'x', 't', 0x0 };

const char *c = "\0This is a text";

char buf1[128];

char buf2[128];

char buf3[128];

size_t lena = sizeof(a) - 1;

size_t lenb = sizeof(b) - 1;

size_t lenc = 15;

memcpy(buf1,a,lena);

memcpy(buf2,b,lenb);

memcpy(buf3,c,lenc);

printf("length a : %d, length b %d, length c %d\n", lena, lenb, lenc);

printf("buf11 : %x, buf21 : %x, buf31 : %x\n", buf11, buf21, buf31);

printf("comparing a with buf1 : %d \n", memcmp(a,buf1,lena));

printf("comparing b with buf2 : %d \n", memcmp(b,buf2,lenb));

printf("comparing c with buf3 : %d \n", memcmp(c,buf3,lenc));

printf("comparing buf1 with buf2 : %d \n", memcmp(buf1,buf2,lena));

printf("comparing buf1 with buf3 : %d \n", memcmp(buf1,buf3,lenc));

printf("comparing buf2 with buf3 : %d \n", memcmp(buf2,buf3,lenb));

return 0;
}
&lt;/pre&gt;
Consider this code. The three text containers a, b and c are initialized differently but all should contain "This is a text" preceded and suffixed by a zero byte.

* Container a's type is an array of char. Its lifetime is limited to the main scope and its initialized content gets put on the stack by the compiler.
* Container b is the longer version of a and is also typed array of char.
* Container c is a pointer to a read-only memory block of chars allocated and initialized by the compiler on the heap.

If compiled with MIPSpro cc or c99 and ran, it becomes apparent that array a is not initialized properly. a1 should contain capital 'T' but instead it's a zero byte: once looking at the stack where a is put with a debugger, there is nothing: The preceding zero byte interferes with compiler code and the stack, although it will allocate the correct amount of bytes on the stack, will only contain zeroes.

This 'shorthand' initialization of an array is often used in modern opensource software, and is particularly prevalent in test suites, where binary headers and unicode data content are initialized in arrays to test functions.

String Concatenation

GCC will accept the following code, by concatenating the strings:

&lt;code&gt;puts( "abc" "def" );&lt;/code&gt;

This is going to not work on MIPSPro's c89, but will on c99. A tutorial on how to fix it is below:

&lt;code&gt;puts( "abcdef" );&lt;/code&gt;

This can work here, alternatively this would too:
&lt;pre&gt;
char buff[ 255 ];

bzero( buff, 0, 255);

strcat( buff, "abc" );

strcat( buff, "def" );
&lt;/pre&gt;

=====Arithmetic On Pointers=====

The gcc compiler allows pointer arithmetic on void pointers. For example, gcc allows

void *foo;

foo += 5;

When using MIPSpro, the pointer must be cast to a type with a size:

void *foo;

foo = (char*)foo + 5;

lvalues

gcc allows the use of casts as lvalues. For example:

void *foo;

(char*)foo += 5;

When using MIPSpro, casts cannot be lvalues:

void *foo;

foo = (char*)foo + 5;

=====Block Expressions=====

gcc allows block expressions, such as ({x++});. When using MIPSPro compilers, remove the extra parentheses.

=====Portable Types=====

Occasionally code that works on other platforms will compile fine on IRIX, but will misbehave when run. These problems can be difficult to track down, but one thing to check for is assumptions about whether char is signed or unsigned. IRIX compilers default to unsigned. It's recommended to check for this.

Setting up parallel debugging sessions and stepping through the working and non-working code simultaneously to find where they diverge is often helpful.

Alternatively, try to recompile the code with the MIPSPro option -signed in CFLAGS. This will treat variables with type char as if they are signed char.

setenv() missing in IRIX

Raion's libxg library has solved this, see it for an example.

=====POSIX Threads and Reentrancy=====

The pthread implementation under Irix is mostly the standard pthreads - there is however a caveat in the form of #defines that are necessary.

&lt;code&gt;CPPFLAGS="-D_SGI_MP_SOURCE -D_SGI_REENTRANT_FUNCTIONS"&lt;/code&gt;

SGI recommended these back when their technical documentation library was a thing - and certainly the first define alters the behavior of the general error indicator errno. Without _SGI_MP_SOURCE individual threads receive separate and unique errno addresses.

If there is unusual behavior regarding threads not sharing or unexpectedly sharing data, one may be missing one of the above.

=====Line terminators=====

The ANSI specification leaves the determination of valid line terminators to the compiler implementors. MIPSpro allows ^J, while GCC allows both ^J and ^M. The &lt;code&gt;to_unix&lt;/code&gt; command will convert files containing DOS-style ^M line terminators to the UNIX standard ^J form.

=====Pseudo Function Macros=====

gcc allows the non-standard &lt;code&gt;__FUNCTION__&lt;/code&gt; and &lt;code&gt;__PRETTY_FUNCTION__&lt;/code&gt; pseudo-macros. These are not true macros, so one must use &lt;code&gt;_GNUC__&lt;/code&gt; to test for them. As of IRIX 6.5.18, the c99 func macro is available, which expands to a function name.

=====Extern Inline Functions=====

The gcc compiler treats extern inline functions as being extern,while the MIPSpro compilers treat them as inline. To get equivalent behavior, remove the inline keyword.

=====Inline defines in C code=====

Pre-c99 C code often define an INLINE macro being set to &lt;code&gt;inline&lt;/code&gt; MIPSPro cc compiler instead uses &lt;code&gt;__inline&lt;/code&gt; MIPSPro's c99 compiler follows the c99 standard and will inline function with the &lt;code&gt;inline&lt;/code&gt; keyword.

getopt_long() missing in IRIX

Raion had added a compat/getopt.h to libxg

=====Compiler Identification=====

To pass specific code using an identification macro, the &lt;code&gt;__sgi&lt;/code&gt; macro can be used to reliably define MIPSPro-related code (or IRIX specific code in general, this can be combined with gnu macros to make paths for both gcc and MIPSPro)

=====Warning Sanitizing=====

MIPSPro is very pedantic with warnings. This can be used in Makefiles to make it less pedantic and behave more like GCC:
&lt;pre&gt;
NOWARN = -woff 1009,1014,1110,1116,1185,1188,1204,1230,1233 \

-Wl,-woff,85,-woff,84
$(CC) $(NOWARN) ...&lt;/pre&gt;

It is highly encouraged to do a normal pass and capture the warnings it gathers anyways, as these can provide some insight into potential mismatches and other issues.

=== C99 Specifics ===
MIPSPro provides C99 compatibility via the c99 driver.

The C99 implementation in MIPSPro is quite good, but unlike standard cc, which is not C99 compliant, it offers far more features:

=== C++-Style Comments ===
By default, the cc driver does not allow // comments to be used. To use //, either use the c99 driver, or set flag -Xcpluscomm in the CFLAGS.

=== Function Macros ===
As previously stated, all versions of IRIX since 6.5.18 support the function pseudomacro.

=== Variadic Macros ===
Supported in c99

=== Format problems in printf for variables with size_t and ssize_t ===
In MIPSPro one cannot use the format strings %zu for size_t types and %zd for ssize_t types. Use %lu and cast both types to unsigned long to print out these variables. Failure to do so will result in unexpected crashes when the program reaches those printf statements.

More to be added as they are discovered.

== Compiler Drivers ==
The driver commands cc, c99, CC, f90, and f77 call subsystems that compile, optimize, assemble, and link source. This section describes the default behavior for compiler drivers.

At compilation time, it is possible to select one or more options that affect a variety of program development functions, including debugging, profiling, and optimizing. It's also possible to specify the names assigned to output files. Note that some options have default values that apply if not specified.

When one invokes a compiler driver with source files as arguments, the driver calls other commands that compile the source code into object code. It then optimizes the object code (if requested to do so) and links together the object files, the default libraries, and any other libraries specified.

Given a source file foo.c, the default name for the object file is foo.o. The default name for an executable file is a.out. The following example compiles source files foo.c and bar.c with the default options:

&lt;code&gt;% cc foo.c bar.c&lt;/code&gt;

This example produces two object files, foo.o and bar.o, and links them with the default C library, libc , to produce an executable called a.out.</text>
    <sha1>f6ba24cfdb1f44ffade1ba17075d608ea6f342d6</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Style Guide</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>6</id>
    <timestamp>2025-02-04T19:31:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2043" xml:space="preserve">In the interest of basic quality standards, TechPubs maintains this page to ensure that all of its editors follow basic guidelines.

=== Formatting ===
By far this is the most imperative section to read. Please read for our standards for page formatting:

- Each subsection must use a Subheading 1 headline.

-  Use &lt;nowiki&gt;&lt;code&gt;&lt;/code&gt;&lt;/nowiki&gt; around single lines of text, use &lt;nowiki&gt;&lt;pre&gt; &lt;/pre&gt;&lt;/nowiki&gt; for blocks

==== Shell Commands ====
As previously stated, use the code tag for shell commands. The format of the command should be as follows:

&lt;code&gt;# command &lt;generic argument&gt;&lt;/code&gt;

For root commands. For user-level commands, use the % sign like this:

&lt;code&gt;% command &lt;generic argument&gt;&lt;/code&gt;

Avoid bashisms or providing bash scripts. If at all possible, write scripts in korn/C shell and use the appropriate shebang. Bash is not a default shell in IRIX, nor is it preinstalled and the sooner bash habits can be unlearned, the better.

== Tone, Writing Style, and Point of View ==
When possible, avoid use of pronouns of any kind unless talking about a specific individual or user. Do not address the reader as "you" and avoid use of "we, I, they, the user, the reader" etc. in writing. If there is a need to refer to someone, use "one" as in "One may wish to heed this section of the style guide.".

When a person's sex is indeterminate, i,e. talking about a user, refer to the person using the person's username. Do not use 'they', 'he' or 'she' if the user's sex is unknown.

All articles should be written with a neutral, professional writing style that uses necessary technical jargon. The audience to keep in mind is a UNIX user with command line experience.

== Edit Wars ==
Edit warring can happen to any wiki, including this one. The appropriate response in this is to contact Raion on the IRIXNet forums immediately in the case of any edit warring. Admins are to adhere to the following rules in judging the appropriate action:

* This Style Guide
* His/her own judgment
* The author of the article (if a Tutorial)</text>
    <sha1>bd7ebf2265bf764e772306b1d75a9fd35152a38d</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>IRIX Install using IRIX Host</title>
  <ns>0</ns>
  <id>5</id>
  <revision>
    <id>8</id>
    <timestamp>2025-02-04T19:36:17Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This article describes the installation of IRIX 6.5.30 on an SGI Fuel. The installation is performed over a local network (LAN), using a SGI Indy workstation as installation server. The main focus of this article is to demonstrate the feature of driving inst using a pre-written command file instead of manually performing all needed software selection steps. Although the example specifically describes an IRIX 6.5.30 installation, the demonstrated methods will work with an..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5888" xml:space="preserve">This article describes the installation of IRIX 6.5.30 on an SGI Fuel. The installation is performed over a local network (LAN), using a SGI Indy workstation as installation server. The main focus of this article is to demonstrate the feature of driving inst using a pre-written command file instead of manually performing all needed software selection steps. Although the example specifically describes an IRIX 6.5.30 installation, the demonstrated methods will work with any 6.5.x installation.

=== Host Server ===
The Host OS/Server should be a recent install of IRIX (i.e. 6.5.22 or later)

Ensure the IP configuration is within the same subnet as the machine installed, i.e. 192.168.1.0/24 This guide will use 192.168.1.7

==== Directory Structure ====
A directory structure has to be created first. The chosen directory names can be different from this example, but they have to be consistent with the following steps:&lt;pre&gt;
% ls /netboot/6.5.30

foundation-1

foundation-2

disc1

disc2

disc3

onc3nfs

devf-13

devlibs

...

fuel.install
&lt;/pre&gt;As an alternative, the overlays can all be combined into a single directory:&lt;pre&gt;
% ls /netboot/6.5.30/install

dist

installtools

stand
&lt;/pre&gt;

==== Permissions ====
All files must be readable by the guest user. This can be accomplished a variety of ways, but two of them are:

chown the files to guest:

&lt;code&gt;# chown -R guest:guest /netboot&lt;/code&gt;

chmod the files to allow world readability:

&lt;code&gt;# chmod -R 755 /netboot&lt;/code&gt;

Next, verify that the guest user is not locked.

It should look similar to this:

&lt;code&gt;guest::998:998:Guest Account:/usr/people/guest:/bin/csh&lt;/code&gt;

Not like this:

&lt;code&gt;guest:*LK*:998:998:Guest Account:/usr/people/guest:/bin/csh&lt;/code&gt;

And also not like this:

&lt;code&gt;guest:XOmXlVxyVdlA2:998:998:Guest Account:/usr/people/guest:/bin/csh&lt;/code&gt;

(Or with a * where the password hash is above)

==== Services ====
Verify that the following services are on:

* tftp
* shell (rsh)

This can be verified in &lt;code&gt;/etc/inetd.conf&lt;/code&gt;

Additionally, add the directory created above to TFTP's line:

&lt;code&gt;tftp dgram udp wait guest /usr/etc/tftpd tftpd -s /usr/local/boot /usr/etc/boot /netboot/6.5.30&lt;/code&gt;

Then reboot or restart inetd using &lt;code&gt;/etc/killall -HUP inetd&lt;/code&gt;

On the off chance IPFilter is enabled, a rule will need to be created to allow the client access.

=== Client Configuration (Fuel) ===
Stop the booting process by pressing the esc key and enter the maintenance menu. Open the "Command Monitor" (or press button 5). Assign a temporary IP address to the machine by setting the following environment variable:

&lt;code&gt;setenv netaddr 192.168.1.174&lt;/code&gt;

&lt;code&gt;setenv srvaddr 192.168.1.7&lt;/code&gt;

The IP has to be in the same subnet as your install server. It is NORMAL for the ping, trace and other utilities to fail from PROM.

The next step is to load the "fx" program and create the needed partitions.

&lt;code&gt;bootp()/netboot/6.5.30/install/stand/fx.64 --x&lt;/code&gt;

The command for older machines like the Indigo2, Indy, O2 etc. is:

&lt;code&gt;boot -f bootp()/netboot/6.5.30/install/stand/fx.ARCS --x&lt;/code&gt;

This is not a tutorial on use of fx, but generally:

* Create a [ro]ot drive.
* Check if the [la]bel contains the bootfile=/unix entry in the bootinfo section. If not, create it.
* [sy]nc the label
* exit fx via /exit

This will revert back to the maintenance menu.

==== Installing IRIX ====
Press button 2 to enter the "Install System Software" menu. Choose "remote directory" and specify the name of the remote host by providing the IP address of the server (192.168.1.7). The name of the remote directory is the one which contains the "sa" file. In this case its "/netboot/6.5.30/install/dist". Press the "install" button to load the installation tools.

Next it will likely be asked to provide IP addresses and hostname of the machine being installed on and to confirm the creation of a fresh XFS file system on the newly created root partition. Do so.

==== Install File ====
Now an installation list can be used to automate the process of setting this up. Here is an example list which can be modified.&lt;pre&gt;
from 192.168.1.7:/netboot/6.5.30/install/dist

open 192.168.1.7:/netboot/6.5.30/foundation-1/dist

open 192.168.1.7:/netboot/6.5.30/foundation-2/dist

open 192.168.1.7:/netboot/6.5.30/devlibs/dist

open 192.168.1.7:/netboot/6.5.30/onc3nfs/dist6.5

open 192.168.1.7:/netboot/6.5.30/devf-13/dist

open 192.168.1.7:/netboot/6.5.30/mipspro_c/dist

open 192.168.1.7:/netboot/6.5.30/mipsproap/dist

open 192.168.1.7:/netboot/6.5.30/mipspro_cee/dist

open 192.168.1.7:/netboot/6.5.30/mipspro_cpp/dist

open 192.168.1.7:/netboot/6.5.30/mipspro744update/dist

open 192.168.1.7:/netboot/6.5.30/prodevworkshop-2.9.5/dist

keep *

install standard

install sysadm_xvm

install sysadm_base

install sysadm_cluster.sw.client

install eoe.sw.xvm

install sysadm_xvm.sw.client

install eoe.sw.xfsrt

install eoe.books

install eoe.sw.xlv

install eoe.sw.xlvplex

install license_eoe

install license_dev

install eoe.sw.uucp

install eoe.sw.quotas

install eoe.sw.ipv6

install eoe.sw.imagetools

install eoe.sw.netman

install eoe.sw.pam

install eoe.sw.pam_dev

install eoe.sw.terminfo

keep appletalk kerberos openssl openssh OpenOffice outbox sgi_apache ftn* gsview ghostscript sgitcl_eoe
&lt;/pre&gt;The final keep command removes obsolete components commonly supplemented with a modern installation of Nekoware or some other distribution.

Now, load the resulting file (with modifications as needed) like this:

&lt;code&gt;admin source 192.168.1.7:/netboot/6.5.30/fuel.install&lt;/code&gt;

After the file runs, check for conflicts with "conflicts". Assuming the version of the file created above has a similar set of commands, it should not be the case. If there's no conflicts, proceed with "go". Once installed, type "quit" and reboot into the newly installed IRIX instance.</text>
    <sha1>5a34a5042a2f39d0ac445f26ec3b705e0dd31e6d</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>IRIX Install using NetBSD Host</title>
  <ns>0</ns>
  <id>6</id>
  <revision>
    <id>9</id>
    <timestamp>2025-02-04T19:44:24Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9432" xml:space="preserve">This article describes installation of IRIX on an Indy, but it should work with slight modifications if applied to other systems. Refer to other installation guides for variance.

This guide should work with a NetBSD machine of any architecture. It has been tested on a Pentium II, Raspberry Pi, and a Power Macintosh.

=== Setup of the Host Server ===
First, install NetBSD onto the host server machine. Great guides already exist for this, so please refer to the NetBSD Handbook for more information.

Record the ip address and hostname of this machine. For the purposes of this article, the following will be used. Replace as needed:

* Hostname: yuuko
* Host IP: 172.16.0.123

The SGI workstation will need to be configured as well with a static ip and hostname. the

following will be used in this document:

* Hostname: mio
* Host IP: 172.16.0.234

This setup requires no additional packages, so pkgsrc and/or pkgin is not necessary.

The following changes must be made to the system:

&lt;code&gt;# mv /bin/sh /bin/psh&lt;/code&gt;

&lt;code&gt;# ln -s /bin/ksh /bin/sh&lt;/code&gt;

The IRIX installation program requires /bin/sh on your host server to accept ksh syntax.

Replacing /bin/sh with the system ksh does not cause any notable problems and satisfies IRIX's requirements.

&lt;code&gt;# printf 172.16.0.123 yuuko &gt;&gt; /etc/hosts&lt;/code&gt;
&lt;code&gt;# printf 172.16.0.234 mio &gt;&gt; /etc/hosts&lt;/code&gt;

The IRIX installation program requires that both the host and target hostnames resolve to their network ip address on the host system.

&lt;code&gt;# mkdir -p /srv/irix/i/22&lt;/code&gt;

This creates the directory structure where installation files will be placed.

&lt;code&gt;# useradd -d /srv/irix/i irix&lt;/code&gt;

This adds a new user, &lt;code&gt;irix&lt;/code&gt;, which the IRIX installer will use to log in and access installation files. This user's home directory is set to the /srv/irix/i folder, under which the installation files will be placed.

=== Configuring TFTP and RSH ===
'''rsh is a very insecure and exploitable service. One should not ever run an rlogin server on any machine that is publicly accessible, that contains sensitive data, or that is on a network that may expose it to attackers. Should someone throw caution to the wind and do it, you risk giving full access to the machine and any data it contains to anyone who asks nicely.'''

Open &lt;code&gt;/etc/inetd.conf&lt;/code&gt; in an editor and find the following lines:

&lt;code&gt;#tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot&lt;/code&gt;

&lt;code&gt;# shell stream tcp nowait root /usr/libexec/rshd rshd -L&lt;/code&gt;

Uncomment both of them by removing the # from the beginning of the line. Then, change tftp's directory from /tftpboot to /srv/irix, so that it looks like this:

&lt;code&gt;tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /srv/irix&lt;/code&gt;

And then, save the file, and restart inet: &lt;code&gt;service inetd restart&lt;/code&gt;

Run the following command, replacing 'mio' with the SGI machine's hostname:

&lt;code&gt;echo "mio +" &gt; /root/.rhosts&lt;/code&gt;

This will enable the IRIX installer to log in as root on the server, which is required for the installer to work.

&lt;code&gt;# echo "mio +" &gt; /srv/irix/i/.rhosts&lt;/code&gt;

This is the same as above, but allowing for the 'irix' user.

=== Prepare the Installation Files ===
As with the other articles here, this assumes that one is grabbing them from the IRIXNet FTP, which has them in tarball, not EFS, format. An explanation of all of the URLs is coming soon.

* Foundation 1
* Foundation 2
* Development Foundation
* Development Libraries
* ONC3NFS

These should be extracted into /srv/irix/i/ resulting in the following directory structure, with each folder containing at minimum a "dist" subdirectory:
&lt;pre&gt;
yuuko# ls /srv/irix/i

devf devl f1 f2 onc3nfs

yuuko#&lt;/pre&gt;

The next set of images is:

* Overlays 1 of 3
* Overlays 2 of 3
* Overlays 3 of 3
* Applications

And for IRIX 6.5.30 only:

* Complementary Applications

For IRIX 6.5.22, these should be extracted into /srv/irix/i/22 resulting in the following

directory structure:
&lt;pre&gt;
yuuko# ls /srv/irix/i/22

apps overlay1 overlay2 overlay3

yuuko#&lt;/pre&gt;

If one is installing 6.5.30, extract into /srv/irix/i/30 instead.

It is also highly recommended to acquire the following distributions, both to ease the

installation process and to provide a better base on which to bootstrap more recent software

once your system is ready:

* Freeware 1 of 4
* Freeware 2 of 4
* Freeware 3 of 4
* Freeware 4 of 4

If acquired as tarballs, one can extract them normally.

If one wishes to install other software distributions such as the MIPSPro C Compiler and Compiler Execution Environment, Performance Co-Pilot, and so on, one can extract those now into /srv/irix/i/ as well.

=== Preparing the Target System ===
Power on the SGI, and press escape or click the button to stop the boot process and enter the maintenance menu. Press '5' or 'enter command monitor', and do the following:
&lt;pre&gt;
&gt;&gt; resetenv

&gt;&gt; setenv -p netaddr 172.16.0.234

&gt;&gt; setenv -p srvaddr 172.16.0.123
&lt;/pre&gt;

This will clear your existing nvram variables, set the machine's ip address, and set the ip address that it will use to contact the host server.

Next, format the drive:

&lt;code&gt;&gt;&gt; bootp()i/22/overlay1/stand/fx.ARCS&lt;/code&gt;

This will bring you into the partitioner. It will ask if one requires extended mode. Answer "no". Use the default values for device name, controller, and drive, unless there's a specific target to install to. And then type the following:
&lt;pre&gt;
fx&gt; r

fx&gt; ro

&lt;enter&gt;
&lt;/pre&gt;
This will tell it to repartition the drive with a root partitioning layout, and accept the default filesystem choice of XFS.

Type 'yes' when it prompts in order to erase the drive.

Then:
&lt;pre&gt;
fx&gt; /label

fx&gt; sy
&lt;/pre&gt;
This will synchronize the disk label .

Then type the following to exit:

&lt;code&gt;fx&gt; exit&lt;/code&gt;

=== Boot the Installer ===
Exit from the command monitor by typing &lt;code&gt;exit&lt;/code&gt;, and then choose the menu option on screen labeled as &lt;code&gt;Install System Software&lt;/code&gt;. Choose "remote directory" and enter the IP address of the server (in this case, 172.16.0.123) and press accept.

For the remote directory, enter 'i/22/overlay1/dist", and press accept, then press install.

This should begin copying installation files to the machine's drive, and then launch into the IRIX installation environment.

On boot, the system will complain about not having a valid filesystem, and ask to create a new one

on &lt;code&gt;/dev/dsk/realroot&lt;/code&gt;. Type 'yes' here. It will ask for a block size. If the drive is under 10G, use 512, otherwise, 4096 is a good choice.

Enter the hostname and address of the new machine (in this case, mio and 172.16.0.234) when prompted. Tt will also prompt you for a netmask. On most home networks this should be 0xffffff00, but one will want to double check to be sure.

This should drop into an &lt;code&gt;inst&gt;&lt;/code&gt; prompt

=== Configure Distribution Sets ===
At the inst prompt, enter the following command:

&lt;code&gt;inst&gt; from yuuko:/srv/irix/i/22/overlay1/dist&lt;/code&gt;

This will set up the installation to pull from the foundation 1 distribution. It will ask now to select a maintenance or feature stream.

Next, open each distribution set that is intended to be installed. In total, one should have at minimum:

* f1
* f2
* devf
* devl
* 22/overlay1
* 22/overlay2
* 22/overlay3
* 22/apps

As well as (optionally):

* onc3nfs

It is imperative not to enter any additional sets such as the freeware distributions until after the

main installation.

Once all of the distributions have been entered, type "done" to return to the installation prompt.

=== Installing Software ===
Firstly, tell the installer to "keep" all packages, which resets the installer's packages to be installed:

&lt;code&gt;inst&gt; keep *&lt;/code&gt;

Then, select the standard meta-installation package:

&lt;code&gt;inst&gt; install standard&lt;/code&gt;

Once it is done, run the following to disable java packages that will cause installation

conflicts:

&lt;code&gt;inst&gt; keep java_* java2_* java3d*&lt;/code&gt;

Optionally, remove obsolete components rarely required:

&lt;code&gt;inst&gt; keep appletalk kerberos openssl openssh OpenOffice outbox sgi_apache ftn* gsview ghostscript sgitcl_eoe&lt;/code&gt;

These are, from left to right:

Appletalk, an old network protocol

Obsolete kerberos, OpenSSL, OpenSSH.

OpenOffice, pretty slow and useless due to its age.

Outbox, a dependency of OpenSSL and a security risk

sgi_apache, an ancient apache server, and a security risk.

ftn*, FORTRAN77/Fortran90 compilers, and not necessary for IRIX.

Ghostscript components

the installed SGI TCL, which conflicts with later TCLs introduced.

These are optional to remove, so mind the choices.

Once this is done, you should see no problems fromthe conflicts command:

inst&gt; conflicts

No conflicts

inst&gt;

At this point, start the install:

&lt;code&gt;inst&gt; go&lt;/code&gt;

That done, grab a cup of coffee, tea, herbal tea, or a bottle or can of beer, soda, seltzer etc. and wait a while.

Once it is completed, the installer will return to the inst prompt. At this point, you can open a new distribution with 'from' to install additional optional software. Otherwise, type 'quit', wait for rqsall to finish, and reboot.

=== Credits, Citations, and Thanks ===
Thank you to forum user "linear" for her guide that was really helpful in making this version. The original is here:

&lt;nowiki&gt;https://paste.sr.ht/~ky0ko/e4bbad9942fe3af5a6b63849baff40b16201a38c&lt;/nowiki&gt;</text>
    <sha1>b3654b84a4d78594d0058b93fbbcb3015694eb62</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>IRIX Setup 101</title>
  <ns>0</ns>
  <id>7</id>
  <revision>
    <id>10</id>
    <timestamp>2025-02-04T19:49:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12417" xml:space="preserve">For newcomers to IRIX, setting up IRIX for the first time can be daunting. This aims to break it down into selective, easy-to-follow sections for a post-install IRIX.

=== Forenotes ===
Due to specificity of various hardware and IRIX versions, this guide primarily assumes IRIX 6.5.21+ and that the user is interested in running Nekoware, optxeno, or another product offered on IRIXNet. It is advised to go into this understanding what the goals of the user are exactly.

Per the Style Guide all root commands will be prefixed with #, all user-level commands will be prefixed with % (for the tcsh shell).

=== First Steps ===

==== Securing root ====
Either login on the login screen to root, or serial in via root. Open a terminal window by clicking Desktop - &gt; Open Unix Shell. This is the root shell of the account, and for clarity sake, most commands will be performed via terminal. Type &lt;code&gt;# passwd&lt;/code&gt; and set a secure password for the root user. If doing this from GUI (i.e. EZSetup, this will cover most of the important settings covered there) be warned IRIX will not accept passwords greater than 8 chars in length. From the commandline, there is no such limitations.

==== Network Setup ====
A detailed article can be found at Network Setup.

==== Date and Time ====
Again, a detailed article can be found at Keeping Time

==== Move $HOME for root ====
Now it is necessary to make a space for root. Due to IRIX's default install, root's home directory is effectively /, the root of the filesystem. '''This is bad. Do not skip this step.'''

Home directories are defined in &lt;code&gt;/etc/passwd&lt;/code&gt;. First, make the directory: &lt;code&gt;# mkdir /root; chmod go-wrx /root&lt;/code&gt; And then update the root line to look like so: &lt;code&gt;root::0:0:Super-User:/root:/bin/tcsh&lt;/code&gt; This can be automated (carefully) with a perl, awk, or sed command, but be careful.

Now clean up: &lt;code&gt;# cd /; rm -rf Desktop dumpster .Sgiresources .cshrc .login .profile .varupdate .wshttymode .desktop-IRIS .desktophost&lt;/code&gt;

Log out and log back in again.

=== Securing IRIX ===

==== Lock unsafe accounts ====
IRIX by default is installed with several accounts without passwords. Checking this is easy: &lt;code&gt;# passwd -as&lt;/code&gt;

Locking the accounts on a normal IRIX install is easy:

&lt;code&gt;# foreach account (lp EZsetup nuucp demos guest OutOfBox sys adm sysadm cmwlogin auditor dbadmin sgiweb 4Dgifts); passwd -l $account; end&lt;/code&gt;

==== Creating a user account ====
Next, create a user account for normal usage, as running as root 24/7 is dangerous. It's easily and safely done using tools in the privbin: &lt;code&gt;# /usr/sysadm/privbin/addUserAccount -l username -S `which tcsh` -H /usr/people/username -C -u 1034 -g 20&lt;/code&gt;

The above example will create a user called '''username''' with a default shell of tcsh, a home directory of &lt;code&gt;/usr/people/username&lt;/code&gt; (/home is NOT a thing on IRIX), create the directory (-C flag) with a uid of 1034 and membership in the user group (ID 20). It may also be advisable to create a group with the same username created by the command above, however that requires manually adding a group to &lt;code&gt;/etc/group&lt;/code&gt; and editing permissions on the home directory. This may be covered in a future installment.

==== Enable Shadow Passwords ====
By default IRIX uses crypt() hashes in /etc/passwd

This is now discouraged and insecure, so it is preferred to enable /etc/shadow. Run &lt;code&gt;pwconv&lt;/code&gt; to enable it.

==== Edit system defaults ====
The file &lt;code&gt;/etc/default/login&lt;/code&gt; controls primary login behavior. Edit the files options to look something akin to this:&lt;pre&gt;
CONSOLE=/dev/console

PASSREQ=YES

ALTSHELL=YES

MANDPASS=YES

UMASK=027

TIMEOUT=60

DISABLETIME=300

MAXTRYS=3

LOGFAILURES=4

IDLEWEEKS=2

PATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11:

SUPATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/etc:/usr/etc:/usr/bin/X11:

SYSLOG=ALL

INITGROUPS=YES

LANG=C

SVR4_SIGNALS=NO

LOCKOUT=4

LOCKOUTEXEMPT=root
&lt;/pre&gt;Note that it is a good opportunity to add extra pathnames that all users will have in PATH. Examples include /usr/nekoware/bin, /opt/xeno/bin, et cetera.

chmod the file to 444 next: &lt;code&gt;# chmod 444 /etc/default/login&lt;/code&gt;

==== File Alteration Monitor ====
For security reasons, edit &lt;code&gt;/etc/fam.conf&lt;/code&gt; to have local_only = true instead of local_only = false.

==== Disable Vulnerable Network Services ====
The following network services are wholly unnecessary for most installations and can be disabled with the following command string:&lt;pre&gt;
# chkconfig sgi_apache off; chkconfig webface_apache off; chkconfig appletalk off; \

chkconfig timed off; chkconfig timeslave off; chkconfig esp off; chkconfig ipaliases off; \

chkconfig ypmaster off; chkconfig yp off; chkconfig sendmail off; chkconfig sendmail_cf off; \

chkconfig webface off; chkconfig named off; chkconfig rsvpd off; chkconfig privileges off
&lt;/pre&gt;Additionally, disabling the following services in &lt;code&gt;/etc/inetd.conf&lt;/code&gt; is prudent, except telnet if an ssh server isn't installed yet, and the system is a server. If that's the case, hold off on that one:&lt;pre&gt;
finger

bootp

tftp

echo

telnet

ftp

discard

chargen

daytime

time

rstatd

walld

rusersd

rquotad

sprayd

ttdbserverd

shell

exec

http

wn-http

ntalk

mountd

sgi_mountd

rexd

bootparam

ypupdated

sgi_videod

sgi_toolkitbus

sgi_snoopd

sgi_pcsd

sgi_pod

sgi_espd

sgi-esphttp

tcpmux/sgi_scanner
&lt;/pre&gt;Some of the above can be re-enabled depending on what is necessary, but the esp ones should not be re-enabled.

==== Secure the X server ====
Edit &lt;code&gt;/var/X11/xdm/xdm-config&lt;/code&gt; and change the DisplayManager*authorize line to read: &lt;code&gt;DisplayManager*authorize: on&lt;/code&gt;

==== Tune the kernel for security ====
Changing these if they are not in use is prudent:&lt;pre&gt;
# printf 'y' | systune ipforwarding 0

# printf 'y' | systune ip6forwarding 0

# printf 'y' | systune icmp_dropredirects 1

# printf 'y' | systune tcp_2msl 60

# printf 'y' | systune allow_brdaddr_srcaddr 0

# printf 'y' | systune tcpiss_md5 1

# printf 'y' | systune restricted_chown 1

# printf 'y' | systune ncargs 131072

&lt;/pre&gt;run &lt;code&gt;# /etc/autoconfig -vf&lt;/code&gt; to rebuild the kernel, and then reboot for full changes to take effect.

==== Install Patches ====
A collection of patches obtained from user backups of sgi.com's support centre is here: &lt;nowiki&gt;http://ftp.irixnet.org/sgi-irix/patches/&lt;/nowiki&gt;

Install all patches for the IRIX version being ran. (inst will not install irrelevant patches on the system).

=== Customizing IRIX ===
Now that security is improved, the actual fun can begin to customizing the IRIX experience.

==== Setup flexlm ====
Place licenses for products in /var/flexlm/license.dat. Softwindows and a few others use different locations. There is a license file in the wiki as well. (search for it!)

==== Enable 24 bit X ====
Unless the graphics in the system are 8-bit (such as an Indy with an XL/8 card), enabling Truecolor will improve the user experience. Edit &lt;code&gt;/var/X11/xdm/Xservers&lt;/code&gt; to be &lt;code&gt;:0 secure /usr/bin/X11/X -bs -nobitscale -c -class TrueColor -depth 24 -solidroot sgilightblue -cursorFG red -cursorBG white&lt;/code&gt;

==== Enable scrollwheel. ====
IRIX by default can't use a scroll wheel. This can be rectified in the kernel:

&lt;code&gt;# systune pcmouse_mode 2&lt;/code&gt;

This sets the scroll wheel to work as on a PC. Mode 3 will set any additional buttons on the mouse to scroll. (it only detects 2 extra buttons)

==== Reduce gamma ====
Set gamma with the following command as root: &lt;code&gt;gamma 1.2&lt;/code&gt; or another value. This will lower the default to a more natural level.

==== Custom tcsh prompt ====
tcsh is a fast, simple UNIX shell that supports most of the same features as bash from an interactive standpoint, and is faster at startup.

Here is a configuration file for root:&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${red}%n${blue}@%m ${yellow}%~ ${red}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;


This sets a red prompt as a reminder. The colors can be changed in the prompt section to one's liking, just don't mess with color values.&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${cyan}%n${blue}@%m ${yellow}%~ ${green}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;And here is a version that is used for normal users.

PATH should be set using &lt;code&gt;setenv PATH '/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11'&lt;/code&gt; and more paths added with a colon-delimited list in the rc file

==== Setting Desktop parameters ====
Use "Desktop-&gt;Customize-&gt;Utilities" from the toolchest menu to specify default applications. Using the full path is necessary. "Desktop-&gt;Customize-&gt;Icons" from the toolchest menu will set the icon size and enable the global setting "Open in Place" which prevents the file manager from creating a new window when opening a new directory.

==== Xdefaults file ====
Here is a sample configuration that dates to the Nekochan.net era:&lt;pre&gt;
*clientDecoration: +resizeh +border +minimize +maximize +menu

*DesksOverview*clientDecoration: none

4Dwm*clock*clientDecoration: none

Overview.geometry: +10-10

Overview*viewWindowName: true

Overview*Frame.marginHeight: 1

Overview*Frame.marginWidth: 1

4Dwm*interactivePlacement: False

4DWm*clientAutoPlace: False

4Dwm*usePPosition: True

4Dwm*positionOnScreen: True

4Dwm*iconImageBackground black

4Dwm*iconImageForeground: white

4Dwm*iconPlacement: left top tight

4Dwm*iconPlacementMargin: 1

4Dwm*resizeBorderWidth: 1

4Dwm*frameBorderWidth: 1

4Dwm*SG_frameOutline: false

4Dwm*SG_titleOutline: false

4Dwm*SG_titlePadding: 0

4Dwm*SG_useDecals: false

4Dwm*iconDecoration: label image
&lt;/pre&gt;The desktop can be heavily customized as needed. To customize 4Dwm, read its manpage

==== Setting up SSH ====
IRIX came with a very old OpenSSH version, and Nekoware has OpenSSH as well. However, these are no longer maintained. A better option is available at SSH Setup on IRIX 6.5.

==== Amend toolchest ====
A full explanation of toolchest is available on its manpage. toolchest reads the following files:&lt;pre&gt;
/usr/lib/X11/system.chestrc

~/.chestrc

~/.auxchestrc

/usr/lib/X11/nodesktop.chestrc

/usr/lib/X11/app-chests/*.chest

/usr/lib/X11/app-defaults/Toolchest

/usr/lib/X11/remote.chestrc

The first three are relevant to most users. To remove entries, remove Itemname in a ~/.auxchestrc is sufficient. Creating entries is easy as well:

menu ToolChest

{

"My Favorite Things" f.menu mystuff

}

menu mystuff

{

"dolphins" f.exec "/usr/demos/bin/atlantis"

"Test Program" f.exec "source ~/.variables;~/testprog"

"games" f.menu mygames

}

menu mygames

{

"flight simulator" f.exec /usr/demos/bin/flight

"arena" f.exec /usr/demos/bin/arena

}
&lt;/pre&gt;Is the manpage example.

==== Setting Backgrounds ====
An article on this is available at Setting Backgrounds

=== Wrapping up ===
This is the end of IRIX Setup 101. For practical reasons this ends most common "first time" setup questions and was patterned after the popular, though poorly-written "IRIX Installation and Customization". Further guides will explore how to perform more advanced configurations.</text>
    <sha1>f48837008812bf31990da28c263739d9f59a1b83</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Setting Backgrounds</title>
  <ns>0</ns>
  <id>8</id>
  <revision>
    <id>11</id>
    <timestamp>2025-02-04T19:52:34Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "IRIX supports out of the box on both 6.5 and pre-6.5 versions customized backgrounds. The procedure varies from version to version, however, as 6.5.22+ supports modern image formats, while versions prior do not.  === Preliminary Steps === Enabling 24-bit X is a major requirement. IRIX Setup 101 has a section on this. Next, copy the backgrounds configuration file.  &lt;code&gt;% cp /usr/lib/X11/system.backgrounds ~/.backgrounds&lt;/code&gt;  ==== Using XPM files (Most versions of IRI..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3189" xml:space="preserve">IRIX supports out of the box on both 6.5 and pre-6.5 versions customized backgrounds. The procedure varies from version to version, however, as 6.5.22+ supports modern image formats, while versions prior do not.

=== Preliminary Steps ===
Enabling 24-bit X is a major requirement. IRIX Setup 101 has a section on this. Next, copy the backgrounds configuration file.

&lt;code&gt;% cp /usr/lib/X11/system.backgrounds ~/.backgrounds&lt;/code&gt;

==== Using XPM files (Most versions of IRIX prior to 6.5.22) ====
IRIX supported 8-bit XPM files relatively early in development. Create a directory to hold backgrounds:

&lt;code&gt;% mkdir ~/backgrounds&lt;/code&gt;

Once the images are added, then create an entry in the .backgrounds file:&lt;pre&gt;
background "Anime"

command "-xpm /usr/people/neko/backgrounds/anime.xpm"

default "-xpm /usr/people/neko/backgrounds/anime.xpm"

readok "/usr/people/neko/backgrounds/anime.xpm"

This is an example created originally by Nekonoko.

The entry will be in Desktop -&gt; Customize -&gt; Background labeled "Anime"
&lt;/pre&gt;

==== Using IRIX's Native PNG/BMP/JPEG handler (6.5.22+) ====
IRIX 6.5.22+ simplified this process greatly. The same entry would be:&lt;pre&gt;
background "Anime"

default "-image /usr/people/neko/backgrounds/anime.jpg"
&lt;/pre&gt;Under 6.5.22.

A Nekochan.net user created this script to automate entry of backgrounds:&lt;pre&gt;
#!/bin/sh

BGDIR=$HOME/backgrounds

cp /usr/lib/X11/system.backgrounds $HOME/.backgrounds

chmod 644 .backgrounds

cd ${BGDIR}

for x in *.jpg *.xpm *.png *.bmp; do

case ${x} in

'*.jpg'|'*.xpm'|'*.png'|'*.bmp') ;;

*)

NAME=`echo ${x} | tr '.' ' ' | awk '{print $1}' | tr '_' ' '`

echo "" &gt;&gt; $HOME/.backgrounds

echo "background \""${NAME}"\"" &gt;&gt; $HOME/.backgrounds

echo "default \""-image ${BGDIR}/${x}"\"" &gt;&gt; $HOME/.backgrounds

;;

esac

done
&lt;/pre&gt;Update the BGDIR variable to change the directory.

=== Using xli ===
In Nekoware, and several other distributions, xli is available and can add the above functionality to older machines. Configure an entry this way:&lt;pre&gt;
background "Anime2"

command "-execute /usr/freeware/bin/xli -onroot -fork /usr/people/neko/backgrounds/anime2.jpg"

default "-execute /usr/freeware/bin/xli -onroot -fork /usr/people/neko/backgrounds/anime2.jpg"

exeok "/usr/freeware/bin/xli"

readok "/usr/people/neko/backgrounds/anime2.jpg
&lt;/pre&gt;xli is the easiest of the two to install as it has no additional dependencies. It's rather dated in that it does not support progressive JPEG or PNG so some backgrounds will need to be converted to standard JFIF or JPEG before xli can deal with them. xli also does not support pseudo transparency effects with some applications, a good example being X-Chat.

There are a couple of caveats to note when using 24-bit images. Desks Overview will not display background previews in the desk panes and desktop switching slows down dramatically, though that's less of an issue on newer hardware.

xli can also add a background to the login screen by editing &lt;code&gt;/usr/lib/X11/xdm/Xsetup&lt;/code&gt; at the top of the file. Add the following:

&lt;code&gt;/usr/nekoware/bin/xli -onroot /path/to/wallpaper/login_pix.jpg&lt;/code&gt;

Note that xli may have a different path installed.

Comments</text>
    <sha1>2c81d80a77415cfd7ec5b0774a1f250b25cab9d5</sha1>
  </revision>
  <revision>
    <id>12</id>
    <parentid>11</parentid>
    <timestamp>2025-02-04T19:52:55Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3179" xml:space="preserve">IRIX supports out of the box on both 6.5 and pre-6.5 versions customized backgrounds. The procedure varies from version to version, however, as 6.5.22+ supports modern image formats, while versions prior do not.

=== Preliminary Steps ===
Enabling 24-bit X is a major requirement. IRIX Setup 101 has a section on this. Next, copy the backgrounds configuration file.

&lt;code&gt;% cp /usr/lib/X11/system.backgrounds ~/.backgrounds&lt;/code&gt;

==== Using XPM files (Most versions of IRIX prior to 6.5.22) ====
IRIX supported 8-bit XPM files relatively early in development. Create a directory to hold backgrounds:

&lt;code&gt;% mkdir ~/backgrounds&lt;/code&gt;

Once the images are added, then create an entry in the .backgrounds file:&lt;pre&gt;
background "Anime"

command "-xpm /usr/people/neko/backgrounds/anime.xpm"

default "-xpm /usr/people/neko/backgrounds/anime.xpm"

readok "/usr/people/neko/backgrounds/anime.xpm"

This is an example created originally by Nekonoko.

The entry will be in Desktop -&gt; Customize -&gt; Background labeled "Anime"
&lt;/pre&gt;

==== Using IRIX's Native PNG/BMP/JPEG handler (6.5.22+) ====
IRIX 6.5.22+ simplified this process greatly. The same entry would be:&lt;pre&gt;
background "Anime"

default "-image /usr/people/neko/backgrounds/anime.jpg"
&lt;/pre&gt;Under 6.5.22.

A Nekochan.net user created this script to automate entry of backgrounds:&lt;pre&gt;
#!/bin/sh

BGDIR=$HOME/backgrounds

cp /usr/lib/X11/system.backgrounds $HOME/.backgrounds

chmod 644 .backgrounds

cd ${BGDIR}

for x in *.jpg *.xpm *.png *.bmp; do

case ${x} in

'*.jpg'|'*.xpm'|'*.png'|'*.bmp') ;;

*)

NAME=`echo ${x} | tr '.' ' ' | awk '{print $1}' | tr '_' ' '`

echo "" &gt;&gt; $HOME/.backgrounds

echo "background \""${NAME}"\"" &gt;&gt; $HOME/.backgrounds

echo "default \""-image ${BGDIR}/${x}"\"" &gt;&gt; $HOME/.backgrounds

;;

esac

done
&lt;/pre&gt;Update the BGDIR variable to change the directory.

=== Using xli ===
In Nekoware, and several other distributions, xli is available and can add the above functionality to older machines. Configure an entry this way:&lt;pre&gt;
background "Anime2"

command "-execute /usr/freeware/bin/xli -onroot -fork /usr/people/neko/backgrounds/anime2.jpg"

default "-execute /usr/freeware/bin/xli -onroot -fork /usr/people/neko/backgrounds/anime2.jpg"

exeok "/usr/freeware/bin/xli"

readok "/usr/people/neko/backgrounds/anime2.jpg
&lt;/pre&gt;xli is the easiest of the two to install as it has no additional dependencies. It's rather dated in that it does not support progressive JPEG or PNG so some backgrounds will need to be converted to standard JFIF or JPEG before xli can deal with them. xli also does not support pseudo transparency effects with some applications, a good example being X-Chat.

There are a couple of caveats to note when using 24-bit images. Desks Overview will not display background previews in the desk panes and desktop switching slows down dramatically, though that's less of an issue on newer hardware.

xli can also add a background to the login screen by editing &lt;code&gt;/usr/lib/X11/xdm/Xsetup&lt;/code&gt; at the top of the file. Add the following:

&lt;code&gt;/usr/nekoware/bin/xli -onroot /path/to/wallpaper/login_pix.jpg&lt;/code&gt;

Note that xli may have a different path installed.</text>
    <sha1>29fac14f4bca4d795e2904a3e622f5255a85478a</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Keeping Time</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>13</id>
    <timestamp>2025-02-04T19:54:27Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Keeping time on IRIX is an easy to do, but less-than well documented thing. This article aims to educate users on the best ways to synchronize, keep time and manage it appropriately.  === UNIX Date and Time === IRIX, like all System V UNIX releases, centers around the &lt;code&gt;date&lt;/code&gt; command for timekeeping purposes. Date can set the time, tell the time, and format time in various fashions, down to the second (a limitation of the UNIX time() syscall). Examples can be f..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1999" xml:space="preserve">Keeping time on IRIX is an easy to do, but less-than well documented thing. This article aims to educate users on the best ways to synchronize, keep time and manage it appropriately.

=== UNIX Date and Time ===
IRIX, like all System V UNIX releases, centers around the &lt;code&gt;date&lt;/code&gt; command for timekeeping purposes. Date can set the time, tell the time, and format time in various fashions, down to the second (a limitation of the UNIX time() syscall). Examples can be found here, not all are directly supported by IRIX.

=== Automating Time Synchronization ===
Historically, IRIX used &lt;code&gt;timeslave&lt;/code&gt; and &lt;code&gt;timed&lt;/code&gt; to synchronize time. Examples of timeslave and timed can be found at those links.

Because of security concerns and how they are unmaintained, there are better alternatives included with IRIX. The simplest is ntpdate which can simply be invoked with &lt;code&gt;ntpdate us.pool.ntp.org&lt;/code&gt;, substituting a proper pool server in the user's home country for the us one. This can be placed into the crontab to run at a regular interval.

&lt;code&gt;ntpd&lt;/code&gt; is also available in SGI Freeware, Nekoware, and many other distributions for synchronizing the time. All that needs to be done is set a list of servers in &lt;code&gt;/etc/ntpd.conf&lt;/code&gt; ('''Warning: not all distributions will put ntpd here!!! Consult the distribution's maintainers if it's unclear where to set it''') and then &lt;code&gt;/etc/init.d/ntp&lt;/code&gt; (or the appropriate source for the initscript) needs to be started for the daemon to run. chkconfig is used to enable the daemon.

=== Timezone ===
Setting the timezone in IRIX is relatively easy. The file &lt;code&gt;/etc/TIMEZONE&lt;/code&gt; (This is case sensitive) is read at boot to set the system timezone. This is a text file and various strings can be inserted. "TZ=:Europe/Berlin" is a valid string, as is "TZ=:EST5EDT" or something similar. The nuances of this are in the &lt;nowiki&gt;https://nixdoc.net/man-pages/IRIX/man5/environ.5.html&lt;/nowiki&gt; environ manpage.</text>
    <sha1>4acae6ff0c4687545f2973190f0d91231f740702</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Network Setup</title>
  <ns>0</ns>
  <id>10</id>
  <revision>
    <id>14</id>
    <timestamp>2025-02-04T19:56:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "IRIX unlike modern Linux distros, Windows and macOS necessitates some level of manual configuration.  Some of the tasks here can be accomplished via the GUI, but it is valuable to understand the networking stack in IRIX.  === Major Components === IRIX's network stack consists of several components:  * inetd - This not only controls the major network services, like telnet and rlogind, it also controls the network and updates to the network necessitate restarts of inetd. *..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3897" xml:space="preserve">IRIX unlike modern Linux distros, Windows and macOS necessitates some level of manual configuration.

Some of the tasks here can be accomplished via the GUI, but it is valuable to understand the networking stack in IRIX.

=== Major Components ===
IRIX's network stack consists of several components:

* inetd - This not only controls the major network services, like telnet and rlogind, it also controls the network and updates to the network necessitate restarts of inetd.
* /etc/hosts - The hosts file, which sets the IP address of the server.
* /etc/nsswitch.conf - This tells IRIX where to obtain various components.
* /etc/resolv.conf - This contains the resolvers IRIX uses, plus the search domain.
* /etc/sys_id - Sets the hostname.
* /etc/config/static-route.options - Sets the default routes in absence of DHCP.
* /etc/config/ipaliases.options - For additional IP addresses.
* routed - Used for DHCP routing.
* autoconfig_ipaddress - DHCP service

With some luck IRIX DHCP will work out of the box, but it's good practice to set static network IPs for management purposes.

=== Static IP Setup ===
What follows is a guide intended to provide a basic set up into setting up network on IRIX 6.5 or later. For older versions, please check Apocrypha

Set the Hostname:

&lt;code&gt;# printf "octane" &gt; /etc/sys_id&lt;/code&gt;

The above command will set the hostname to octane. Set it as desired by replacing the string inside the quotes. This does NOT include the domain name.

==== Assign IP Address ====
To self-assign an IP, open up the /etc/hosts file and remove the IRIS line. Then, add the following line:

&lt;code&gt;192.168.1.10 octane.home.local octane&lt;/code&gt;

This line should be the desired IP, followed by the fully qualified hostname, and the hostname at the end.

==== Turning off DHCP and routed ====
Now, disable these:&lt;pre&gt;
# chkconfig autoconfig_ipaddress off

# chkconfig routed off
&lt;/pre&gt;

==== IP Aliasing ====
This step is optional, but if more IP addresses are required, they can be added.

First, verify the default interface:&lt;pre&gt;
% /usr/etc/ifconfig -a

tg0: flags=8f15c43&lt;UP,BROADCAST,RUNNING,FILTMULTI,MULTICAST,CKSUM,DRVRLOCK,LINK0,L2IPFRAG,L2TCPSEG,IPALIAS,HIGHBW,IPV6&gt;

inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255

lo0: flags=8001849&lt;UP,LOOPBACK,RUNNING,MULTICAST,CKSUM,IPV6&gt;

inet 127.0.0.1 netmask 0xff000000
&lt;/pre&gt;lo0 is the localhost loopback, so the default will generally be the other interface, unless there's many cards, in which case, it's a matter of trial and error if not known.

In any case, once determined, move on to setting aliases. Edit &lt;code&gt;/etc/config/ipaliases.options&lt;/code&gt;, adding aliases using the following syntax:

&lt;code&gt;tg0 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255&lt;/code&gt;

Now turn on the service:

&lt;code&gt;# chkconfig ipaliases on&lt;/code&gt;

==== DNS ====
Next, edit /etc/resolv.conf with DNS servers and search domains:

nameserver 208.67.222.222 # This is OpenDNS

nameserver 1.1.1.1 # This is Cloudflare, also recommended

domain home.local

To ensure that this file is correctly permissioned, run:

&lt;code&gt;# chmod 644 /etc/resolv.conf&lt;/code&gt;

==== nsswitch.conf ====
This step ensures that rogue NIS/yp services don't interfere. If planning to use NIS/yp, skip this step.

Change the hosts line to read: "hosts: files dns"

==== Routing ====
Finally, add a static route to the default gateway in &lt;code&gt;/etc/config/static-route.options&lt;/code&gt;. It is necessary to know this for this guide to work.

&lt;code&gt;$ROUTE $QUIET add net default 192.168.1.1&lt;/code&gt;

Reboot and the network should start working.

=== IPv6 ===
IRIX includes support for IPv6 and it can be enabled as follows:

First, tune the kernel:

&lt;code&gt;systune ip6_enable 1&lt;/code&gt;

Then reboot.

Due to some bugs, it's necessary to check strings in the ipv6 files:

&lt;nowiki&gt;#&lt;/nowiki&gt; strings /var/ns/lib/libns_dns.so | grep ip6&lt;pre&gt;
ip6.arpa.

ip6_rtld
&lt;/pre&gt;</text>
    <sha1>84ae67e07b404e050c47aae2944db525cb2be99f</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Upgrading O2 from R5-7k to R10-12k</title>
  <ns>0</ns>
  <id>11</id>
  <revision>
    <id>15</id>
    <timestamp>2025-02-04T19:57:34Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5773" xml:space="preserve">It is possible to upgrade an SGI O2 from R5000/7000 CPUs to R10000/12000 CPUs. The process takes about an hour and requires some specific parts.

=== Prerequisites: ===

* An SGI O2 with the latest PROM (4.18) and preferred 6.5.22 or later installed.
* A chassis that will accept an R10K/R12K CPU module. There are essentially 3 breeds of chassis out there, R5K only with no removable drive divider, R5K with removable drive divider and finally an R10K/R12K chassis where the divider is already missing.
* An R10k or 12k PIMM (Processor/CPU module) and the 4-screws and tray it sits in.
* The three screws used to secure the plastic tray to the motherboard (one screw from the underside) and the motherboard tray (two screws, slightly longer from the top). These are machine screws and cannot be reused from an R5000 module.
* A suitable motherboard tray, this has different side and rear panels to accommodate the gap where the extra drive would have been in the R5K chassis. It also has a slightly different backplate which has an extra screw fitting.
* CPU stand off connectors. This is where it gets really tricky as these are not readily obtainable. These are probably the hardest to come by of the whole upgrade.
* PCI Riser for R10000/12000 models. The PCI riser pcb contains a little Dallas chip with the O2’s hardware address on it, hence it cannot be omitted.

Every other piece of the O2 can be reused.

=== Process ===
Step 1. Unplug the O2 and remove the power supply. Do not skip this step, as it will fry the chassis frontplane and other pieces.

Step 2. If the O2 chassis has a drive divider panel, unscrew the two screws for it and remove it by sliding it out of the unit.

Step 3. Remove the rear PSU cover and black top cover, followed by the rear components : Power supply, drives, AV module and system board tray. Next, on the top of the unit unscrew the two outer skin retaining screws that hold the skin to the optical drive outer tray / cover. Remove the blue (purple for O2+) outer skin by lifting it up and place to one side, out of harms way.

Step 4. Remove the optical drive holder by unscrewing the two screws near the front of the metal enclosure. Slide the drive and enclosure forward to unplug the power cable and SCSI ribbon.

Step 5. Remove the bottom skirt. Turn the machine over and stand it on its head. Make sure to unplug the speaker cable from the frontplane connector before removing the skirt. The bottom panel (or skirt) is held on with two black indent tabs and a series of plastic prongs that fit into the chassis. The two indent tabs simply prevent the skirt from sliding sideways and keeps the tabs engaged in the chassis.

Step 6. To remove the frontplane, take off the shiny metal cover / faceplate. Have a look at the corners of the cover, there are tabs with round ridged protrusions holding this to the chassis, simply push these in slightly and it should be able to slide out slowly. To stop the faceplate / cover from bending, work loose all the corners then pull it away a bit at a time. Once exposed, unscrew the frontplane from the chassis.

Step 7. Remove PCI tray and riser assembly. Press the lever above the CPU module down and it should slide out with some gentle wiggles.

Step 8. Remove the RAM modules by pressing both sides of the tabs down completely, and then pulling the modules out. Remove the CPU carrier by removing the retaining screws on the plastic, the CPU should come off with it. The CPU and carrier lifts off quite easily, do not twist while pulling the module.

Step 9. Remove the two R5K CPU stand offs (little white plastic risers) using a very small flat screw driver (Such a jewelers or eyeglass screwdriver) or blade edge. The stand-offs clip onto the motherboard connector and can be pried off where they clip on to the motherboard quite easily.

Step 10. Next up, remove the rear IO panel screws that hold the motherboard to the backplate and tray. The motherboard slides out for an inch or so, and it will lift up and out at a bit of an angle. (If an FP1600 adapter card is installed, remove it prior to attempting this.) Replace the backplate. The backplate is held on with a few screws and IO hex nut screws, it’s a simple swap. While the motherboard is out, it's a good opportunity to clean the tray and board.

Step 11. Slide the motherboard back in and screw the metal backplate to the tray, it’s reverse procedure again. Now fit the R10K/R12k risers, they can only go on in one direction / orientation, do not force them on. If they don’t want to slide on easily, they are probably oriented the wrong way.

Step 12. Replace the FP adapter or other accessory boards.

Step 13. Next up fit the R10K/R12K CPU PIMM carrier to the motherboard and screw in the top two screws. Turn the motherboard and tray over and screw in the slightly shorter screw from the bottom. Ensure all three screws are fitted.

Step 14. Turn the assembly back over again and fit the CPU to the carrier tray, gently push the CPU onto the little riser connectors, once again do not twist while applying light pressure. The module screws in with 4 machine screws. Make sure the CPU is properly seated on the risers, otherwise the boot process will fail.

Step 15. Fit The R10K/R12K PCI riser card and PCI tray, followed by RAM modules.

The motherboard is now prepared at this stage.

Step 16. Reinstall the power supply, motherboard, A/V board and boot drive. Test the machine. If the machine boots with a solid red light, remove the motherboard and reseat the CPU module, applying gentle pressure to fully seat it.

Step 17. Double check the hinv and env variables in command monitor, ensure the boot drive is using disk(2)

=== Sources ===
&lt;nowiki&gt;http://forums.irixnet.org/thread-578.html&lt;/nowiki&gt;</text>
    <sha1>3568af8e04afd464bc090efa3bc3ba6d0fc77e8b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>IRIX 101</title>
  <ns>0</ns>
  <id>12</id>
  <revision>
    <id>16</id>
    <timestamp>2025-02-04T19:59:03Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5284" xml:space="preserve">This guide aims to educate new users to IRIX about the differences between IRIX and other UNIX and Unix-like systems. This includes through FAQs, explanations of how some parts of the OS work, and how a new user can adjust to these changes easily.

=== A Brief History of IRIX ===
IRIX began life as an evolution of two earlier projects, GL2 and RISCOS (a product by MIPS Computer Systems, not the Acorn RISC OS), the latter of which was acquired by Silicon Graphics in 1992. GL2 code from the 68000-based IRIS machines was ported to System V R3, making 4D1-3.x - the immediate predecessor of IRIX de jure, but defacto IRIX under the hood. 4D1-3.x utilized NeWS in the form of 4Sight, replacing MEX, the windowing system on GL2. When SGI acquired MIPS Computer Systems, RISCOS had many things taken from it to form IRIX 4, which used XSGI and the familiar 4DWM instead of 4Sight. IRIX now steadily advanced, with 6.x introducing XFS, and 6.5 introducing many more HPC elements to the OS. The last major release was 6.5 in 1998, but the OS continued minor development until 2006 with the discontinuation of all MIPS development by SGI and the migration to IA-64 and GNU/Linux, ending the reign of IRIX and effectively relegating it to maintenance mode.

Throughout the 1990s, IRIX was influential in many industries such as HPC, education, scientific, 3D graphics (Autodesk Maya began life as PowerAnimator on IRIX for example) and music production. This legacy is a huge contribution to continued hobbyist development of IRIX.

=== Frequently Asked Questions ===
1. Is IRIX related to GNU/Linux?

IRIX's XFS filesystem was ported to the Linux kernel and continues to be a major filesystem on GNU/Linux. Beyond that, IRIX is entirely different, predating Linux by years of development.

2. What systems does IRIX run on?

IRIX runs on MIPS workstations produced by SGI, and a modified version of it underpins UNICOS/mp on the Cray X1 and X1E. Other than that, it cannot run on anything else.

3. What does IRIX use for GUI?

IRIX, like most UNIX systems uses X11, a proprietary variant called XSGI, and the window manager is called 4DWM - standing for 4D Window Manager (early SGI machines were called 4D, and this also hearkens back to 4Sight and 4D1, the old name for IRIX).

4. Why are machines that run IRIX expensive?

There are no new machines being produced, and high-end machines are in short supply. Less expensive machines can be had. We do not recommend using eBay to search, as the prices are usually extremely inflated.

5. What shell does IRIX use? It doesn't behave like Bash!

Most UNIX do not use bash. IRIX uses tcsh and ksh as shells. tcsh is the one that has many of the features users are after (history, tab completion of arguments, repeat last argument (!$, not ESC-.), and thus the recommended interactive shell. However, should a user prefer it is possible to use bash from Nekoware, or other sources. It's not recommended to replace the root shell with bash, however.

6. What startup system does IRIX use?

IRIX uses a customized System V init. It is not the same as GNU/Linux's former default (sysvinit).

7. Where are eth0, sda1, and why does ifconfig show nothing unless I append -a?

IRIX, similar to BSDs and System V UNIX OSes, names devices by driver, not type. The disk naming scheme is similar to Solaris and illumos, /dev/dsk/dksXdXsX, or disk, scsi bus id, drive id, slice ID. ifconfig shows nothing unless -a is hit because it's not the same code as GNU/Linux.

8. Where can I get the source to IRIX?

IRIX is closed source, and there was no major release of the source during its lifetime. Community efforts to free it from limbo are ongoing.

9. Is USB supported?

Only HID, USB audio and some controllers are supported. No USB mass storage or cameras or anything like that.

10. Can I mount an ISO of IRIX software?

No, not within IRIX. IRIX has no loopback filesystem support. Additionally, IRIX software is distributed on EFS CDs, not Joliet/rockridge/iso9660 (the format that is specified by .iso) so don't use .iso - use .efs or .img

11. My backspace key doesn't work.
This is common on some configurations. To fix, type the following sequence into a shell: &lt;code&gt;stty erase CTRL-V BACKSPACE&lt;/code&gt; the caps indicate actual keys to hit, not actual things to type. This should result in either stty erase

H or stty erase
? or something similar.
12. CTRL-C doesn't do SIGINT

Fixable. &lt;code&gt;stty intr ^C&lt;/code&gt;

Both 11 and 12 can be permanently solved by adding those commands to .cshrc or .bashrc or .profile, depending on the shell used and such.

13. Where is nano?

GNU nano never was packed with IRIX. Get used to using vi, that's the default commandline editor. There's jot as well, a graphical editor, and nedit. Nano is available from many distributions.

14. Can IRIX be emulated?

MAME currently supports (slow) emulation of IRIX. Do not use qemu-irix - it's not designed to run actual IRIX software, it's designed as a hack for N64 devs to use the IDO/MIPSPro compilation suite to reverse engineer N64 games.

15. Inst doesn't help with dependencies

IRIX is from an era where dependencies needed to all be supplied at once or in-order for a package manager to work. It does not currently support dependency resolution at all.</text>
    <sha1>f1bfda9459d6ee24daa5a56dc0bb22fad5f8d48d</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Installing IRIX</title>
  <ns>0</ns>
  <id>13</id>
  <revision>
    <id>17</id>
    <timestamp>2025-02-05T04:15:57Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="805" xml:space="preserve">It is recommended to install IRIX via a network for ease of use. IRIX has a rather unique and comprehensive network installing method, and as a result of it's convenience, performance and utility, many users have created guides on how to do it. This serves as the meta hub. 

=== General ===
The following network protocols must be used to network install IRIX:

* rsh
* tftp
* bootp

The host must in most cases be a UNIX compatible with UNIX permissions, on the same LAN. IRIX PROMs do not possess routing, ICMP echoes (It cannot respond to pings), or the ability to take HTTP or rsync.

=== Guides ===
This subsection offers specific guides for installation with various host operating systems.

==== IRIX ====

* [[IRIX Install using IRIX Host]]

==== NetBSD ====

* [[IRIX Install using NetBSD Host]]</text>
    <sha1>86e8540066e4b741a4d4ed045ed5af343fcc8028</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:4D50GT.jpg</title>
  <ns>6</ns>
  <id>14</id>
  <revision>
    <id>20</id>
    <timestamp>2025-02-05T04:44:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">A 4D/50 GT Professional IRIS</text>
    <sha1>0f83ce45cded02b2edbc04ec848bc5827f9852a2</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Prime-IRIS.jpg</title>
  <ns>6</ns>
  <id>15</id>
  <revision>
    <id>21</id>
    <timestamp>2025-02-05T04:46:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">A rebadged Professional IRIS</text>
    <sha1>27fbfed847eac5f632a66e707ac22814e3422c5a</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Professional IRIS</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>22</id>
    <timestamp>2025-02-05T04:47:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1914" xml:space="preserve">The first widely produced MIPS powered SGIs, these systems were historically called the IRIS 4D GT series. Commonly called the "Twin Towers" due to the distinctive look caused by the disks being kept in a smaller sidecar tower, these systems are notable for being among the most rare and undocumented MIPS powered SGIs. Released firstly as the 4D/60, then as three models, the high end 4D/80, the midrange 4D/70 and the low end 4D/50 differing by CPU and graphics configuration, and the ultimate 4D/85 released in late 1988. The "Twin Towers" design seems to have carried over into the early POWERSeries systems released much later.
[[File:4D50GT.jpg|thumb]]

=== Hardware ===
The unusual Twin Tower design is the result of engineering decisions that led to the smaller tower containing the disk array of the system, with the larger tower containing the graphics boards. This concept of two asymmetrical towers is distinctive and appears unreplicated by anyone but SGI.

The heart of each system is a MIPS R2000 MIPS I 32-bit RISC CPU, replacing the earlier IRIS 2000 and 3000 model line powered by the Motorola 68000 line. Each system's CPU board could hold a maximum of 16MB RAM, with the 4D/80 allowing an additional set of boards totaling 144MB.

The Clover 1 and 2 systems, called G and GT respectively (for Graphics, and Graphics, Textured presumably) were the primary graphics options of the systems.

Similar to other IRIS4D machines, they used a DB9 custom serial keyboard and mouse, similar to the Personal IRIS.

Some reports point to a 4D/85 Single tower model being offered, but little to nothing is known about it.
[[File:Prime-IRIS.jpg|left|frame]]

=== Operating System Support ===
The Personal IRIS line was available during the "IRIX 3.x" era, but more contemporaneously called 4D1-3.x UNIX era. Support continued into IRIX 4.x and 5.x, and was removed along with all other 32-bit options by 5.3.</text>
    <sha1>293aa1c55c4198570cc5229f18621dacc725cd65</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:PersonalIris.jpg</title>
  <ns>6</ns>
  <id>17</id>
  <revision>
    <id>23</id>
    <timestamp>2025-02-05T16:58:05Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="36" xml:space="preserve">A 4D/35 Personal IRIS owned by CB_HK</text>
    <sha1>1e3b754c56f4f02a34d7e3562df77b26a254fd8c</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Personal IRIS</title>
  <ns>0</ns>
  <id>18</id>
  <revision>
    <id>24</id>
    <timestamp>2025-02-05T16:58:54Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4767" xml:space="preserve">The Personal Iris was introduced in 1988 as low end workstation to the IRIS 4D series based on MIPS RISC microprocessors. A model name consists of "4D/" and a code designating the CPU and graphics type. The models replaced the "Twin Tower" style Professional IRIS series on the low end market, with the [[Power Series]] taking the higher end market. All Personal IRIS systems use a 32-bit MIPS I core and share some parts commonality with the R3000 Indigo in the 30 and 35 models. The last model (4D/35) was introduced in 1991 and presumably sold through 1993 with the release of the Indy heralding the end of the IRIS line.
[[File:PersonalIris.jpg|thumb|A 4D/35 owned by CB_HK of IRIXNet]]

=== Models ===
The series came in four models differentiated by badging, and the contents of the system module inside the case. No major external differences are otherwise shown. Between the 4D/2x and the 4D/3x systems are major differences. The latter one uses a totally different system board which besides faster processors includes a newly designed memory interface that allows much higher bandwidth and a larger amount of main memory. The system bus of the newer boards is clocked at 30 MHz instead of 10 MHz.
{| class="wikitable"
|Model
|CPU board
|CPU
|Maximum Memory
|-
|4D/20
|IP6
|MIPS R2000 12.5 MHz
|32MB
|-
|4D/25
|IP10
|MIPS R3000 20 MHz
|32MB
|-
|4D/30
|IP14
|MIPS R3000 30 MHz
|128MB
|-
|4D/35
|IP12
|MIPS R3000 36 MHz
|128MB
|}
The 20 and 25 models use industry standard 30-pin SIMMs. The 30 and 35 models use the same RAM modules as the Indigo R3000.

=== Graphics ===
The Personal IRIS had either a Datastation (Server) configuration, or they could utilize VME-based Eclipse or Express graphics, the latter only being usable on the 30 and 35 models due to a common architecture with the [[IRIS Indigo]]

=== Peripherals ===
The Personal IRIS, unlike later SGIs, does NOT possess support for PS/2 and uses the 4D-style DB9 keyboards used by the Personal/Professional IRIS series. To use PS/2 peripherals necessitates an adapter.

Personal IRIS models 4D/20 and 4D/25 have basic audio capabilities onboard. For audio in 4D/30 and 4D/35 an optional board is required that is plugged into a special slot on the mainboard. That additional board is called Magnum Audio Option and offers 16bit/stereo audio instead of the 8bit/mono audio that was offered on the earlier Personal Iris models.

The Personal IRIS has a built in SCSI controller that supports the internal as well as the external SCSI devices. The SCSI connector is located on the back of machine itself (just right of the E-Module) and is also covered by the plastic skin. The internal drives connect to the same SCSI chain that is also available via that external centronics SCSI port. The SCSI controller is narrow SCSI, Western Digital 33C93A.

All Personal IRIS systems allow the owner to install double height 6U VME devices. The VME interface of the Personal Iris also supports busmaster devices which may directly access the main memory of the computer. Only the 4D/30 and 4D/35 models allow VME block transfer due to a new peripheral controller on the system board.

=== Operating System Support ===
The Personal IRIS line was available during the "IRIX 3.x" era, but more contemporaneously called 4D1-3.x UNIX era. Support continued into IRIX 4.x and 5.x, and was removed along with all other 32-bit options by 5.3.

=== Hardware Problems ===

==== Power Supply ====
Power supply problems are not uncommon with these systems. Unplug the power cord, then open the opposite side of the E-Module and remove the sheetmetal. The power supply has 2 replaceable fuses which are worth to check as well as the proper cabling. One fuse is on the small daughtercard, the other is next to that card and usually covered with a blue plastic cap.

==== Onboard Battery ====
Signs of failure: The system fails to boot and returns to PROM after issuing "Can't set tod clock"

This problem has so far been seen only on the later Personal Iris models (4D/30 and 4D/35). The earlier systems may not be affected and just boot with a faulty date/time.

While there also may be other causes, the by far most likely is an empty battery on the CPU board. The original battery is a 3V coin cell made by Duracell (DL2450). The battery is socketed so replacing it doesn't require any soldering. The cost of the battery is approximately 3 USD / 2 EUR.

==== 4MB Memory Modules ====
Signs of failure: System doesn't work when more than one set of 4MB modules is installed.

This is a known problem and a flaw in the systems hardware of 4D/30 and 4D/35 systems which can not be fixed. The bottom line is, that only one 16MB kit (4x4MB) may be installed - there is no limitation regarding 8MB (4x2MB) or 32MB (4x8MB) kits.</text>
    <sha1>f3dfc8d393cbf5a87d830234b38321f34014fb65</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Nekochan.net</title>
  <ns>0</ns>
  <id>19</id>
  <revision>
    <id>25</id>
    <timestamp>2025-02-05T17:05:31Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial Commit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1785" xml:space="preserve">Nekochan.net was a website registered on January 21st, 2000 according to public WHOIS. It was founded by Nekonoko, real name Peter Plank, who started it for the purpose of discussing SGI software and hardware. In 2003, the Nekochan forums were started and Nekochan.net became an intensely popular icon in the Silicon Graphics community as the main hub for non-corporate users of SGI hardware and software. It was shut down May 21st, 2018 under alleged GDPR compliance issues.

=== History ===
Nekochan.net's founder Peter Plank was a very private individual, but what is known of him is that he is/was a very enthusiastic collector of vintage machines of various kinds, but especially SGI software/hardware.

The assets of Nekochan.net were drawn by Peter himself, and he even had a manga called Rimu Revolution.

Nekochan.net's forums were the primary SGI community from 2003 through 2017, when competitors began to pop up.

=== Contents ===
The main domain was a blog powered by "Movable Type", a popular early 2000s blog software which was used to announce nekoware packages and the like. 

The forums hosted more than 2,000 members and 15 years of posts. It had its heyday prior to 2010 and by 2018 it was described by many as a "ghost town, old man's club, or elitist shithole"

The wiki was preserved onto wiki.preterhuman.net but many articles were out of date or plain wrong. TechPubs, which descends from the later [[IRIXNet]] wiki, supersedes many articles. 

The gallery is preserved at IRIXNet's Silicon Image [https://siliconimage.irixnet.org/index.php/nekochan-gallery-archive]

=== Legacy ===
[[IRIXNet]] was the first community to try and capture the same audience. It was joined by the [[Silicon Graphics User Group]] in early 2020. Other sites have popped up as well.</text>
    <sha1>bfeb6b66ef0743be68de34530dea8cdebb56d56e</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>IRIXNet</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>26</id>
    <timestamp>2025-02-05T18:06:23Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial Commit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="875" xml:space="preserve">IRIXNet, short for IRIX Network, is a Silicon Graphics-focused website, forum and archive of former hobbyist sites that was founded in 2017 by Raion (Kaz Kuroi) and Praetor (George). It was founded with the express purpose of providing a secondary Silicon Graphics site separate to [[Nekochan.net]] due to recent concerns of downtime at the time, and to facilitate open sales of commercial software. 

=== Contents ===
IRIXNet has an archive, file servers, gallery and forums. It exists as one of two English language SGI-related sites offering forums, the other being [[Silicon Graphics User Group]].

=== Association with TechPubs ===
TechPubs is owned by Raion, who also owns IRIXNet, but the purpose of Techpubs is far more focused on documentation and to serve as an SEO-friendly SGI instructional website. It does not inherit the moderation team or policies of IRIXNet.</text>
    <sha1>3f09c04cbd3a4622afb86c1b179e261cfc8f99cd</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>IRIX</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>27</id>
    <timestamp>2025-02-05T18:07:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial Commit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4087" xml:space="preserve">'''IRIX''' is a System V based UNIX operating system developed by Silicon Graphics, Inc. (SGI) to run natively on their MIPS workstations and servers. It takes the basis of System V, adds BSD and proprietary extensions. IRIX is the operating system on which many innovations were pioneered and later ported to other operating systems, including OpenGL, the XFS filesystem, and GLX extensions.

The last major version of IRIX was IRIX 6.5, released in May 1998. New minor versions of IRIX 6.5 were released every quarter until 2005; since then there have been four further minor releases. Through version 6.5.22, there were two branches of each release: a maintenance release (identified by an m suffix to the version number) that included only fixes to the original IRIX 6.5 code, and a feature release (with an f suffix) that included improvements and enhancements. An overlay upgrade for prior versions (6.5.1-21) was made available free of charge. 6.5.23 - 6.5.30 required an active support contract with SGI, which is no longer available due to Silicon Graphics International's acquisition by HP Enterprise. Security patches and hotfixes were available through December 2013 when the last SGI support contracts expired.

=== History ===
The IRIX name was first used around the time of release 3.0 of the operating system for SGI's IRIS 4D series of workstations and servers, in 1988. Previous releases were identified only by the release number prefixed by "4D1-", e.g. "4D1-2.2". The 4D1- prefix continued to be used in official documentation to prefix IRIX release numbers.

IRIX 3.x is based on UNIX System V Release 3 with 4.3BSD enhancements, and incorporated the 4Sight windowing system, based on NeWS and IRIS GL. SGI's own Extent File System (EFS) replaced the System V filesystem.

IRIX 4.0, released in 1991, replaces 4Sight with the X Window System (X11R4), the 4Dwm window manager providing a similar look and feel to 4Sight.

IRIX 5.0, released in 1993, incorporated certain features of UNIX System V Release 4, including Executable and Linkable Format executables.

In 1994, IRIX 6.0 added support for the 64-bit MIPS R8000 processor, but was otherwise similar to IRIX 5.2. Later 6.x releases supported other members of the MIPS processor family in 64-bit mode. IRIX 6.3 was released for the SGI O2 workstation only. IRIX development stabilized with IRIX 6.5, released in 1998. The last version of IRIX was 6.5.30, released in August 2006.

Since around 2001 SGI had been moving its efforts to Linux and Microsoft Windows but MIPS/IRIX customers had forced it to continue to support that platform through 2006. On September 6 of that year, an SGI press release heralded the end of the MIPS/IRIX product line. Production ended on December 29, 2006, with last deliveries in March 2007, except by special arrangement. Support for these products ended in December 2013 and they will receive no further updates.

=== Features ===
IRIX 6.5.x is compliant with UNIX System V Release 4, UNIX 95 and POSIX (including 1e/2c draft 15 Access Control Lists and Capabilities).

IRIX has strong support for real-time disk and graphics I/O. IRIX was among the first widely available UNIX version to feature a graphical user interface for the main desktop environment. IRIX continues to serve niche roles in some media production houses and scientific modeling, long after other competitors have surpassed its capabilities.

IRIX was a leader in Symmetric Multiprocessing, scalable from 1 to greater than 1024 processors with a single system image made possible by its use of Cray/NUMALinking, acquired from SGI's purchase of Cray.

IRIX used the IRIX Interactive Desktop, which by default used the 4Dwm X window manager with a custom look based on the Motif Window Manager. Performance Co-Pilot is another product made famous by IRIX.

The Open64 compiler began life as the MIPSPro compiler, the primary compiler for SGI IRIX.

IRIX was the first operating system to implement system wide OpenGL for desktop applications, games, and rendering applications such as Alias Power Animator.</text>
    <sha1>94b5ca020c8ae3e30d700c149b5523332a53032a</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Porting Issues</title>
  <ns>0</ns>
  <id>22</id>
  <revision>
    <id>28</id>
    <timestamp>2025-02-05T18:08:32Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1935" xml:space="preserve">This page aims to catalogue issues porting programs to IRIX, and common solutions available both first and third party.

=== Missing Headers ===
Some common missing headers on more modern UNIX installations include:

* endian.h - Defines endian byteswapping functions. Partially implemented in Libxg (Big Endian Functions Only!)
* setenv.h - Defines setenv() (doesn't exist on IRIX)

=== Differences in threading ===
IRIX pthreads have some known differences from GNU/Linux, BSD and Solaris, which sometimes introduces incompatibilities.

=== CLOCK_MONOTONIC ===
This function sets a hardware counter unaffected by wall time (system time). IRIX has this functionality in &lt;code&gt;&lt;sys/ptimers.h&gt;&lt;/code&gt;, it is called CLOCK_SGI_CYCLE.

=== Autoconf issues ===
IRIX keeps some old libraries around which should be ignored by some GNU programs and programs that assume that every library should be used.

Trying this should work:

ac_cv_lib_gen_getmntent=no \

ac_cv_lib_sun=no \

ac_cv_lib_sun_getpwnam=no \

ac_cv_lib_sun_getmntent=no \

ac_cv_lib_sun_yp_match=no \

ac_cv_lib_socket=no \

ac_cv_lib_socket_main=no \

./configure...

=== Dirent issues ===
IRIX has dirent.h but its struct doesn't name a number of types. There's two common errors seen, the first involves d_nameln. The others involve dirfd(), and d_type.

Both can be solved easily. For the first, strlen(dp-&gt;d_name) can replace the dp-&gt;d_nameln . For the other, add a define guard for #define dirfd(dp) (((DIR *) dp)-&gt;__dd_fd) for SGI systems. This exists on both GCC and MIPSPro. d_type is not as easily fixed.

=== err.h and __progname issues ===
These are common BSDisms and easily worked around. For the err.h functions, most can be replaced with fprintfs to stderr or stdout, depending on context. __progname can be determined via PATH_MAX variable assuming one knows the exact positions in the array to look for. IRIX-neweoe has examples in the grep implementation.</text>
    <sha1>4538c7739ba47fbb206e9115ebe07d6bd3b3e08a</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Libxg</title>
  <ns>0</ns>
  <id>23</id>
  <revision>
    <id>29</id>
    <timestamp>2025-02-05T18:10:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial Commit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1230" xml:space="preserve">libxg, or libxenograft, is a small, compact and portable library for IRIX 6.5 to add commonly used functions in BSD and Linux to IRIX in a lighter weight format than GNULib, and under the permissive BSD 3-clause license.

=== Characteristics ===
Libxg uses a simple POSIX makefile and C99 programming standards. It is derived from OmniOS, NetBSD and OpenBSD code.

Libxg provides the following functions as of June 2020:

asprintf() &lt;asprintf.h&gt;

forkpty() &lt;forkpty.h&gt;

getopt_long() (and a replacement getopt() function, both use &lt;compat/getopt.h to avoid name collisions)

setenv() &lt;setenv.h&gt;

strndup() &lt;strndup.h&gt;

strtonum() &lt;strtonum.h&gt;

unsetenv() &lt;setenv.h&gt;

vasprintf() &lt;asprintf.h&gt;

It also provides an endian.h file.

=== Programming Guide ===
To link against the shared library, make sure to pass the n32 flag to the program to link against and use -lxg in the link flags alongside other libs.

To compile statically, include the /usr/lib32/libxg.a file in the final build

For including the functions in a project that needs porting, it is necessary to add guards to include the appropriate header files for IRIX

==== Where to get ====
Currently libxg is available at [https://codeberg.org/SolusRaion/libxg Codeberg]</text>
    <sha1>1880b421ef9453cde48d20f26dfbe70fab515d46</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Neweoe</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>30</id>
    <timestamp>2025-02-05T18:15:09Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="503" xml:space="preserve">neweoe is an IRIXCE project started by Kazuo Kuroi to provide replacements for IRIX utilities and programs 

=== Rationale ===
IRIXCE consists of security updates to FOSS libraries, new commands ported from NetBSD, OpenBSD, OmniOS/illumos operating systems, as well as some clean-room IRIX code. It provides userland support for IRIX-related projects. 

=== Where to get ===
The code for it can be found at [https://codeberg.org/SolusRaion/irix-neweoe Codeberg]. It is also packaged in IRIXCE patchsets.</text>
    <sha1>edda94338c2f58fb960f2c5667bbf7c22e400a30</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>LTO Drives</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>33</id>
    <timestamp>2025-02-05T18:21:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6666" xml:space="preserve">
LTO drives, also called Ultrium drives, are magnetic tape backup drives that can store larger amounts of data than DAT/DDS drives can and are well-supported under IRIX.

=== Configuration ===
To configure an LTO drive requires a configuration to be placed in /var/sysgen/master.d/scsi.

=== Compatibility ===
Most documented cases include LTO1 through 4 drives. Others could potentially work but have not been tried.

=== Examples ===
&lt;pre&gt;
/* HP Ultrium 1 / LTO-1 */
{ DATTAPE, TPDAT, 2, 7, "HP", "Ultrium", /*LTO-1*/, 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_COMPRESS|MTCAN_PREV|
MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
MTCAN_SILI|MTCAN_SEEK|MTCAN_CHTYPEANY,
/* minimum delay on i/o is 4 minutes, because when a retry is
* performed, the drive retries a number of times, and then
* rewinds to BOT, repositions, and tries again. */
40, 5*60, 20*60, 20*60, 3*3600, 512, 512*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* IBM LTO-2 / Ultrium-TD2 */
{ DATTAPE, TPDAT, 3, 11, "IBM", "ULTRIUM-TD2", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* IBM LTO-3 / Ultrium-TD3 */
{ DATTAPE, TPDAT, 3, 11, "IBM", "ULTRIUM-TD3", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Quantum SuperDLT-1 */
{ DECDLT, TPDLT, 7, 9, "QUANTUM", "SuperDLT1", 0, 0, {0},
MTCAN_BSF | MTCAN_BSR | MTCAN_APPEND | MTCAN_SPEOD |
MTCAN_CHKRDY | MTCAN_VAR | MTCAN_SETSZ | MTCAN_SILI |
MTCAN_SEEK | MTCAN_SYNC | MTCAN_CHTYPEANY | MTCAN_COMPRESS,
20, 8*60, 20*60, 5*60, 3*3600, 4096, 64*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* HP LTO3 / Ultrium 3 */
{ DATTAPE, TPDAT, 2, 9, "HP", "Ultrium 3", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|MTCAN_PART|MTCAN_PREV|
MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
MTCAN_SILI|MTCAN_AUDIO|MTCAN_SEEK|MTCAN_CHTYPEANY|MTCAN_COMPRESS,
40, 5*60, 20*60, 20*60, 3*3600, 512, 512*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Certance LTO-2 / Ultrium 2 */
{ DATTAPE, TPDAT, 8, 9, "CERTANCE", "ULTRIUM 2", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },

&lt;/pre&gt;&lt;pre&gt;
/* Quantum LTO3 / Ultrium 3 */
{ DATTAPE, TPDAT, 8, 9, "CERTANCE", "ULTRIUM 3", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|MTCAN_PART|MTCAN_PREV|
MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
MTCAN_SILI|MTCAN_AUDIO|MTCAN_SEEK|MTCAN_CHTYPEANY|MTCAN_COMPRESS,
40, 5*60, 20*60, 20*60, 3*3600, 512, 512*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* HP LTO4 / Ultrium 4 */
{ DATTAPE, TPDAT, 2, 9, "HP", "Ultrium 4", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|MTCAN_PART|MTCAN_PREV|
MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
MTCAN_SILI|MTCAN_AUDIO|MTCAN_SEEK|MTCAN_CHTYPEANY|MTCAN_COMPRESS,
40, 5*60, 20*60, 3*3600, 512, 256*512, 512*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Quantum SDLT220 drive */
{ DECDLT, TPDLT, 7, 7, "QUANTUM", "SDLT220", 0, 0,
{0}, MTCAN_BSF | MTCAN_BSR | MTCAN_APPEND | MTCAN_SPEOD |
MTCAN_CHKRDY | MTCAN_VAR | MTCAN_SETSZ | MTCAN_SILI | MTCAN_SEEK|
MTCAN_SYNC | MTCAN_CHTYPEANY | MTCAN_COMPRESS | MTCAN_SETDEN,
20, 8*60, 20*60, 5*60, 3*3600, 4096, 64*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;


/* Quantum SDLT320 drive */
{ DECDLT, TPDLT, 7, 7, "QUANTUM", "SDLT320", 0, 0,
{0}, MTCAN_BSF | MTCAN_BSR | MTCAN_APPEND | MTCAN_SPEOD |
MTCAN_CHKRDY | MTCAN_VAR | MTCAN_SETSZ | MTCAN_SILI | MTCAN_SEEK|
MTCAN_SYNC | MTCAN_CHTYPEANY | MTCAN_COMPRESS | MTCAN_SETDEN,
20, 8*60, 20*60, 5*60, 3*3600, 4096, 64*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Quantum SDLT600 drive */
{ DECDLT, TPDLT, 7, 7, "QUANTUM", "SDLT600", 0, 0, {0, 0, 0, 0 },
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SPEOD |
MTCAN_CHKRDY|MTCAN_VAR| MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|
MTCAN_SYNC|MTCAN_CHTYPEANY | MTCAN_COMPRESS | MTCAN_SETDEN,
20, 8*60, 20*60, 5*60, 3*3600, 16384, 64*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names, tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },

&lt;/pre&gt;&lt;pre&gt;
/* SONY GY-8240 DTF2 drive */
{ SONYGY, TPGY2120, 4, 7, "SONY", "GY-8240", 0, 0, {0, 0, 0, 0},
MTCAN_BSF | MTCAN_BSR | MTCANT_RET | MTCAN_CHKRDY | MTCAN_PREV |
MTCAN_SEEK | MTCAN_APPEND | MTCAN_SILI | MTCAN_VAR | MTCAN_SETSZ |
MTCAN_CHTYPEANY | MTCAN_COMPRESS,
20, 100*60, 10*60, 9*60, 9*60, 16384, 256*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names, tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* IBM LTO-2 / Ultrium-TD2 */
{ DATTAPE, TPDAT, 3, 11, "IBM", "ULTRIUM-TD2", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Certance LTO-2 / Ultrium 2 */
{ DATTAPE, TPDAT, 8, 9, "CERTANCE", "ULTRIUM 2", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;</text>
    <sha1>2c6a70a64390c05ca9da6eb5069ccc46540435e1</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>EFS</title>
  <ns>0</ns>
  <id>27</id>
  <revision>
    <id>35</id>
    <timestamp>2025-02-05T18:57:06Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="709" xml:space="preserve">The Extent File System was the default filesystem used by IRIX from GL2-W2.4 (pre-IRIX 4.x) through IRIX 5.3. Additionally, it was the filesystem used for all CDs produced for IRIX by SGI.

=== History ===
EFS was introduced in GL2-W2.4, a pre-IRIX System V based product to replace the original System V UFS. It was deprecated starting in 1994, with the release of an IRIX 5.3 XFS distribution, and replaced by XFS with IRIX 6.0 on all new installs.

=== Specifications ===
The EFS filesystem is relatively primitive by modern standards, being a synchronous (non-journaling, no soft updates) filesystem with a fixed block size of 512 bytes. The maximum filesystem size is 8G, and the maximum file size is 2G.</text>
    <sha1>c6bf6031367dd773e2b417b083d848d5ea28b7bb</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>ARCS</title>
  <ns>0</ns>
  <id>28</id>
  <revision>
    <id>36</id>
    <timestamp>2025-02-05T18:58:16Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "ARCS is the name for the firmware used by SGI machines to boot an IRIX kernel and store important NVRAM variables. It's also commonly called in common parlance the '''PROM''' by users, though this generally refers to the physical chip storing ARCS.  === Capabilities === ARCS is a fully graphical firmware that has basic understanding of TCP/IP (though it can't ping/trace and has no understanding of routes. It only knows TFTP and RSH commands enough to boot a kernel or app..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1999" xml:space="preserve">ARCS is the name for the firmware used by SGI machines to boot an IRIX kernel and store important NVRAM variables. It's also commonly called in common parlance the '''PROM''' by users, though this generally refers to the physical chip storing ARCS.

=== Capabilities ===
ARCS is a fully graphical firmware that has basic understanding of TCP/IP (though it can't ping/trace and has no understanding of routes. It only knows TFTP and RSH commands enough to boot a kernel or application like fx), it can boot CD, Tape and Network installations of IRIX.

=== Command Monitor ===
The Command Monitor is the area most users will have the most interest in learning as it contains useful commands to set common startup variables for IRIX and the system in general, preparing the system for remote network installs, and displaying installed hardware (hinv).

==== Commands ====
This section will cover useful commands and their functions:

hinv - Hardware inventory. Displays installed and detected hardware, usually disks, network controllers, CPU, memory etc. Similar to the IRIX command, but far more limited.

setenv - changes environment variables to change the behavior of the system.

printenv - prints all active env variables

fill - sets portions of the NVRAM memory to new values - notable for use in fixing the SGI Indy's MAC address failures.

==== Variables ====
netaddr - the default IP of the system.

console - sets graphical (g) or serial console (d). Serial will always work, but d will explicitly ignore the graphics adapter.

AutoLoad - will the system automatically load and boot its disk? y / n parameters.

hostname - default hostname, used for network booting.

eaddr - MAC address of the host.

SystemPartition - The partition that contains the startup code for the SGI.

OSLoadPartition - The partition that contains the operating system.

OSLoader - sets the shell or loader used. Usually sash (standalone shell).

OSLoadFilename - the filename of the kernel used. /unix for IRIX.</text>
    <sha1>ac94b54ab564238c0d94da7e2f2000ae272cbacc</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>L1 Controller</title>
  <ns>0</ns>
  <id>29</id>
  <revision>
    <id>37</id>
    <timestamp>2025-02-05T18:58:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "All of the systems based on the Chimera architecture (Fuel, Origin 3000, Onyx4, Origin/Onyx 3x0, Tezro) include a low-level hardware monitor, power management and startup/shutdown system called the L1 controller. This system does many things that earlier systems either lacked the capability of doing, or had a separate system that performed those functions, including holding serial numbers and configuring NUMA access.  === Power commands === To start an L1 equipped SGI, t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="974" xml:space="preserve">All of the systems based on the Chimera architecture (Fuel, Origin 3000, Onyx4, Origin/Onyx 3x0, Tezro) include a low-level hardware monitor, power management and startup/shutdown system called the L1 controller. This system does many things that earlier systems either lacked the capability of doing, or had a separate system that performed those functions, including holding serial numbers and configuring NUMA access.

=== Power commands ===
To start an L1 equipped SGI, type &lt;code&gt;pwr up&lt;/code&gt; and hit return. &lt;code&gt;pwr down&lt;/code&gt; shuts the system off.

=== Serial commands ===
Oftentimes when reconstructing a multi-node Origin system, the node bricks will not have matching serials. To clear a serial, type &lt;code&gt;serial clear&lt;/code&gt; but it is advised to only do this on bricks with mismatched serials that can recover them from other bricks. To disable serial security, and copy serials from an L2 controller or other bricks, type &lt;code&gt;let the carnage begin&lt;/code&gt;.</text>
    <sha1>66e068c5acfed1c45236876bfb2edf565b26b1cd</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Toolchain</title>
  <ns>0</ns>
  <id>30</id>
  <revision>
    <id>38</id>
    <timestamp>2025-02-05T19:01:17Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The toolchest program is the IRIX equivalent of a Start menu or a "dock". The standard set of menu buttons in the IRIX Interactive Desktop toolchest is Desktop, Selected, Find, System, and Help.  === Change the Toolchest Display === The following flags can be used to change the behavior/look of the toolchest:  - horizontal - The toolchest will display horizontally instead of vertically.  - vertical - The toolchest will display vertically. This is the default.  - decal -..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4232" xml:space="preserve">The toolchest program is the IRIX equivalent of a Start menu or a "dock". The standard set of menu buttons in the IRIX Interactive Desktop toolchest is Desktop, Selected, Find, System, and Help.

=== Change the Toolchest Display ===
The following flags can be used to change the behavior/look of the toolchest:

- horizontal - The toolchest will display horizontally instead of vertically.

- vertical - The toolchest will display vertically. This is the default.

- decal - On by default, the toolchest will display a decal next to each entry.

- icon - When the toolchest is not in use, it is relegated to an icon.

- nodecal - disables decals

- hidetitle - disables the titlebar

- showtitle - enables the titlebar

- title - allows the user to set the title to something other than Toolchest

=== Config files ===
&lt;pre&gt;
/usr/lib/X11/system.chestrc

~/.chestrc

~/.auxchestrc

/usr/lib/X11/nodesktop.chestrc

/usr/lib/X11/app-chests/*.chest

/usr/lib/X11/app-defaults/Toolchest

/usr/lib/X11/remote.chestrc
&lt;/pre&gt;This is a list of config files that Toolchest reads. The first three are most relevant to users, the nodesktop version is used in a minimal IRIX install.

==== Configuration ====
As specified in the manpage for Toolchest, the menu tree is always rooted at a menu named "ToolChest"; thus the &lt;code&gt;Menu ToolChest { ... }&lt;/code&gt; must be provided somewhere in the Toolchest config file. The .auxchestrc file is included by the system.chestrc file, and thus it's the recommended way to update the Toolchest, as it will include changes made systemwide. .chestrc, by comparison, does not.

The format for Toolchest config files are based around a subset of the mwm (Motif Window Manager) configuration files, but with a few custom extensions. Toolchest recognizes the keyword menu and the operators f.menu, f.title, f.exec, f.separator, and f.label. In addition, the new keywords remove, include, and sinclude and the new operators f.checkexec, f.checkexpr, f.exec.sh, f.checkexec.sh, f.checkexec.sh.le, and f.checkexpr.sh have been added.

The remove keyword will remove an entry. If one writes &lt;code&gt;remove Overview&lt;/code&gt; then it will remove all buttons named Overview. If one writes &lt;code&gt;remove Overview from Toolchest&lt;/code&gt; it will remove it from that specific menu, Toolchest (lower levels are ignored). If a button has separators above and below it, one will be removed.

The include/sinclude keywords will include a file or directory that is listed after them. sinclude will silently fail (no message) while include will error out if it cannot access the file, i.e. if it doesn't exist. A directory that's included will be searched for all files ending with the extension .chest.

The f.checkexec operator specifies the command to be executed when a button is clicked. Unlike f.exec, it will gray itself out if there's a problem that prevents it from executing, i.e. the executable is not installed, is missing, not executable etc. It is therefore recommended over f.exec.

f.checkexpr is a related operator that is used to provide a double-quote delimited argument (rather than a single, spaceless argument with checkexec) allowing for shell one-liners to be executed on the Toolchest.

These also have .sh versions in the latest versions of IRIX, which will force them to be ran by /bin/sh instead of by $SHELL or $MWMSHELL. These are recommended for speed, but the older ones are offered for backwards compatibility reasons.

=== Examples ===
Below is an example provided in the toolchest manpage, detailing how to nest specific menus properly in a cascading relationship.&lt;pre&gt;
menu ToolChest

{

"System" f.menu system

no-label f.separator

"Windows" f.menu windows

no-label f.separator

"Tools" f.menu tools

no-label f.separator

"Demos" f.menu demos

}

menu tools

{

"Tools" f.title

"Shell" f.checkexec.sh.le "xterm"

no-label f.separator

"Showmap" f.checkexec.sh.le "/usr/sbin/showmap"

"Makemap" f.checkexec.sh "/usr/sbin/makemap"

"Clocks" f.menu clocks

}

menu clocks

{

"" f.title

"Square Clock" f.checkexec.sh.le "/usr/sbin/clock"

"Analog Clock" f.exec.sh "xclock"

"Round Clock" f.checkexec.sh.le "oclock -bg black -fg \"dark red\""

"Digital Clock" f.exec.sh "xclock -digital"

}
&lt;/pre&gt;</text>
    <sha1>7628636e95fa3d7cbbf5b398b77e4682e0cd8e32</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Inst</title>
  <ns>0</ns>
  <id>31</id>
  <revision>
    <id>39</id>
    <timestamp>2025-02-05T19:03:20Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "inst is the package and installation utility on IRIX, and is supplemented by swmgr, an graphical frontend (the relationship is similar to aptitude and synaptic) to the command line.  inst is used for installing and uninstalling programs, applying patches and more.  === General Operations === inst can be started from within IRIX by typing "inst" as root to access the full menu, but it can be run as a user, but it will be read-only.  Entries in inst are numbers and accessi..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1905" xml:space="preserve">inst is the package and installation utility on IRIX, and is supplemented by swmgr, an graphical frontend (the relationship is similar to aptitude and synaptic) to the command line.

inst is used for installing and uninstalling programs, applying patches and more.

=== General Operations ===
inst can be started from within IRIX by typing "inst" as root to access the full menu, but it can be run as a user, but it will be read-only.

Entries in inst are numbers and accessible by pressing the corresponding number. A user may also automatically specify tardists or directories using the -f option.

"list" will list, depending on the view setting, either the distributions or target (installed programs) that are open.

"step" will allow a user to select subsystems one by one.

"close" will close a distribution, removing it from inst.

"keep" is used to return a subsystem to its normal state, meaning if its marked for installation it won't be installed, and if it's marked for removal it'll be retained.

"install" is used to install a subsystem, and remove is used to remove it.

"conflicts" is the dependency management system and ensures that all dependencies are met.

"go" starts the queue and will proceed, barring any conflicts, to perform the functions.

=== Locally Installing Programs ===
Much like Windows, IRIX has provisions for local installs too. Assuming that the user activating inst owns the directory specified with -r, it'll run:

&lt;code&gt;inst -r /usr/people/owner/ -f neko_zlib_1211.tardist&lt;/code&gt;

For example will, if ~/bin is owned by owner, will open inst and allow the program to be installed in that prefix. This can be useful to offer multiple versions of the same program or allow multiple seats to have different software installed.

=== Administration ===
During a miniroot installation, the administration area can be used to setup network and perform other operations.</text>
    <sha1>8db756f371399cdc6a1c0a73890aa5e8f9c7c5d3</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>NFS</title>
  <ns>0</ns>
  <id>32</id>
  <revision>
    <id>40</id>
    <timestamp>2025-02-05T19:07:19Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "NFS or Networked File System is a protocol used to share filesystems over a network. IRIX includes support for NFSv2 and NFSv3.  === Hosting NFS === '''NFSv2 and NFSv3 have known security problems and exploits. It's highly advised to use a proper firewall and configuration.'''  NFS can be hosted from IRIX, BSD, Solaris/illumos, Linux or even some versions of macOS and still retain compatibility to IRIX. This page documents related issues with NFSv3/2 and the various quir..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2542" xml:space="preserve">NFS or Networked File System is a protocol used to share filesystems over a network. IRIX includes support for NFSv2 and NFSv3.

=== Hosting NFS ===
'''NFSv2 and NFSv3 have known security problems and exploits. It's highly advised to use a proper firewall and configuration.'''

NFS can be hosted from IRIX, BSD, Solaris/illumos, Linux or even some versions of macOS and still retain compatibility to IRIX. This page documents related issues with NFSv3/2 and the various quirks to get it working on each host OS.

=== Recommended Hosts ===
The easiest hosts to get working with IRIX are, in no particular order:

* illumos/Solaris
* FreeBSD
* NetBSD
* IRIX 6.5.22 or higher
* Windows 10 Pro or Enterprise

=== Not Recommended ===
These hosts have a number of server and implementation issues with NFSv3, if there are tricks unheard of yet to getting them working please feel free to add tricks below:

* Linux: rpcbind in Linux is buggy, and the nfsd module usually gets interfered with by SELinux, systemd and other modern Linuxisms.
* macOS: The most recent versions do not appear to have proper NFSv3 support for hosting, though NFSv3 connections do appear to work.

=== Guides ===

==== FreeBSD ====
FreeBSD supports NFSv3 for IRIX easily.

'''Enabling Services'''

The following lines must be added to the /etc/rc.conf file:&lt;pre&gt;
rpcbind_enable="YES"

nfs_server_enable="YES"

mountd_enable="YES"

mountd_flags="-r -p 735"
&lt;/pre&gt;Now start the services:

&lt;code&gt;# service rpcbind start; service nfsd start; service mountd reload&lt;/code&gt;

'''Exporting'''

On ZFS, do not use /etc/exports. Instead, use:

&lt;code&gt;zfs sharenfs="-network 10.0.0.0 -mask 255.255.255.0" tank/protected&lt;/code&gt;

This will share the tank/protected dataset on LAN addresses 10.0.0.0/24

Further examples will include PF firewall rules to ensure spoofed/hostile traffic cannot compromise NFS.

==== Linux (Ubuntu) ====
Thanks to Larbob/lbdm for this guide.

'''Preparation'''

Install the NFS subsystem:

&lt;code&gt;sudo apt install nfs-kernel-server&lt;/code&gt;

Make an NFS share directory:

&lt;code&gt;sudo mkdir -p /srv/nfs&lt;/code&gt;

Set up /etc/exports with something like this:

&lt;code&gt;/srv/nfs 192.168.0.0/24(rw,sync,no_subtree_check,no_root_squash)&lt;/code&gt;

Edit /etc/default/nfs-kernel-server's RPCMOUNTDOPTS section to add --no-nfs-version 4

'''Finishing Touches'''&lt;pre&gt;
sudo exportfs -ra

sudo systemctl restart nfs-config

sudo systemctl restart nfs-kernel-server
&lt;/pre&gt;This will provide a setup to allow anyone with uid 0 to write as root. Please be careful if deciding this.</text>
    <sha1>42153ae157f5237360e2b7c615b7873f0ee4885b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Swap</title>
  <ns>0</ns>
  <id>33</id>
  <revision>
    <id>41</id>
    <timestamp>2025-02-05T19:07:55Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Just like on some other UNIX systems, IRIX can use swap. This article explains how to enable swapfiles for more swap.  === General Procedure === &lt;pre&gt; # mkfile -v 2048m /usr/swap  /usr/swap 2147483648 bytes  # swap -a /usr/swap &lt;/pre&gt;This will enable the file immediately. To ensure it works next boot add the following line to /etc/fstab:  &lt;code&gt;/usr/swap swap swap pri=3 0 0&lt;/code&gt;"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="383" xml:space="preserve">Just like on some other UNIX systems, IRIX can use swap. This article explains how to enable swapfiles for more swap.

=== General Procedure ===
&lt;pre&gt;
# mkfile -v 2048m /usr/swap

/usr/swap 2147483648 bytes

# swap -a /usr/swap
&lt;/pre&gt;This will enable the file immediately. To ensure it works next boot add the following line to /etc/fstab:

&lt;code&gt;/usr/swap swap swap pri=3 0 0&lt;/code&gt;</text>
    <sha1>54c2bef8d8e5e4f0f9eb12234df6cf703b38a5fa</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>SSH Setup for 6.5</title>
  <ns>0</ns>
  <id>34</id>
  <revision>
    <id>42</id>
    <timestamp>2025-02-05T19:09:16Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "For years, SSH has been a pain under IRIX. However, with a recent port of Dropbear, an embedded, secure, and lightweight SSH server and client implementation for IRIX, it is now possible to have reasonably fast SSH usage under IRIX.  === What is Dropbear? === Dropbear is an OpenSSH alternative, in a word. OpenSSH is a great product, but it does have its downsides. Recent versions are hard to setup under IRIX as it wants security features more and more that are difficult..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1749" xml:space="preserve">For years, SSH has been a pain under IRIX. However, with a recent port of Dropbear, an embedded, secure, and lightweight SSH server and client implementation for IRIX, it is now possible to have reasonably fast SSH usage under IRIX.

=== What is Dropbear? ===
Dropbear is an OpenSSH alternative, in a word. OpenSSH is a great product, but it does have its downsides. Recent versions are hard to setup under IRIX as it wants security features more and more that are difficult to disable. It's also considerably slower on IRIX than dropbear is.

=== Is Dropbear "safe"? ===
It's actively developed by Matt Johnston and other volunteers. It's no more dangerous than OpenSSH being ran, and if a user properly configures his or her firewall, then it is unlikely to be hacked. It is miles ahead, as well, of using public telnet.

=== Where can one get Dropbear? ===
Raion has currently packaged it for optxeno, with intent to include it in Nekoware II.

=== How to setup Dropbear? ===
Once optxeno is downloaded and extracted to /opt/xeno, do the following:

&lt;nowiki&gt;#&lt;/nowiki&gt; mkdir -p /opt/xeno/etc/dropbear

&lt;nowiki&gt;#&lt;/nowiki&gt; chmod 700 !$

&lt;nowiki&gt;#&lt;/nowiki&gt; /opt/xeno/sbin/dropbearkey -t ecdsa -s 521 -f /opt/xeno/etc/dropbear/host.key
&lt;nowiki&gt;#&lt;/nowiki&gt; /opt/xeno/sbin/dropbear -r /opt/xeno/etc/dropbear/host.key
This should start dropbear, which can be checked with ps -aef | grep dropbear. It should be running on local port 22, barring IPFilter or any other blockages.

=== How to autostart Dropbear? ===
Dropbear supports inetd usage, but it appears finnicky under IRIX and will probably necessitate further poking at it. Additionally, it would be great to get an initscript for installation/packaging, but it has not been quite figured out yet.</text>
    <sha1>db29885d2439b17e537b04f890cee84770e015d5</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Transporting SGIs</title>
  <ns>0</ns>
  <id>35</id>
  <revision>
    <id>43</id>
    <timestamp>2025-02-05T19:09:51Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This page is a list of user/crowd sourced notes on how to transport various systems. This page is free to be edited, as long as preexisting content is not removed without notification of a staff member.  === Onyx === The Onyx was available in two form factors, known as the Deskside (codename ''Eveready'') and the Rack (codename ''Terminator'', sometimes referred to as the Rackmount or, rarely, Rackside). While both systems are large computers, the Rack is significantly l..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5307" xml:space="preserve">This page is a list of user/crowd sourced notes on how to transport various systems. This page is free to be edited, as long as preexisting content is not removed without notification of a staff member.

=== Onyx ===
The Onyx was available in two form factors, known as the Deskside (codename ''Eveready'') and the Rack (codename ''Terminator'', sometimes referred to as the Rackmount or, rarely, Rackside). While both systems are large computers, the Rack is significantly larger. Perhaps due to the rarity of images of both systems side-by-side, it is a common misconception that the dimensions of the rack are equal to that of two desksides stacked vertically — in reality, the rack is significantly larger than the deskside in all dimensions. For an accurate size comparison with the two systems in a single picture, see the official Onyx product image, from the SiliconGraphics website circa 1994, below.

The Deskside measures 26 inches in height, 21 inches in width, and 29 inches in length, with a minimum weight of 195lbs. It is worth noting that while 195lbs is a minimum for the system, many deskside Onyxes will be significantly heavier, as the installation of additional components can increase weight significantly. Transporting a deskside Onyx is a difficult, though not impossible task. Small wheels on the bottom make rolling the system directly forwards and backwards relatively easy, though rotating the system will likely require lifting it by the metal handle at the rear of the system. This handle provides a convenient and strong point to lift or turn the system if necessary, and is accessible with or without the installation of plastic skins. If the system must be transported up or down stairs, at least two strong people are required. It is recommended that, during lifting, the system be held at the front and back, as the sides provide no good grip points and the bottom rests too close to the floor to set the system down without repositioning one's fingers. The metal handle provides a good grip at the rear of the system. For the front, it is recommended that the large plastic piece covering the front of the system be removed entirely and transported separately, so that the ventilated metal "box" above the cardcage can be used as a second handhold. Do not attempt to lift the system by its drive slots, skins, or purple front drive door, as none of these parts are strong enough to support the weight of the system. Improper transport of an Onyx deskside can result in damage to the system and its surroundings, as well as injury, so be sure to devise a plan before moving the system, especially where stairs are involved.

The Rack measures 62 inches in height, 27 inches in width, and 48 inches in length, with a minimum weight of 560lbs. Like the Deskside, this can increase drastically as parts are added, with the system's manual listing its maximum weight as 800lbs. Transporting a Rack Onyx is more difficult, simply due to the larger size of the system. While, like the deskside, it is equipped with wheels, the greater weight makes lifting the system very difficult when fully assembled. SGI reseller Ian Mapleson suggests on his website that buyers looking to purchase a Rack Onyx from him remove heavy components such as the exterior panels, the two front doors, the blower fans, and the OLS power supply units before attempting to transport the system, saying that "general mobility (eg. if it has to be moved up some steps) can be greatly improved". While weight can be further reduced by removing the system's boards, Ian notes that it is "only wise to do this if the boards can be properly packed, etc.". He also suggests the rental of a cube van with a lift gate to aid in loading and unloading of the system, and points out that "A truck's tail lift also allows one to maneuver the system over many steps if required".

=== Onyx2 ===
The Deskside Onyx2 will be covered in this section. The system is a cuboid approx 20x24x27" and weighing from 170lbs to over 300lbs. The unit does have wheels. To transport safely, the best way is to remove the skins and transport them separately. Failing that, it is possible to transport the system without damage very carefully. In order to do so, get a hand truck or push dolley and using a towel to cushion it, carefully slide it up onto the dolley. It can then be hoisted into a truck and carefully padded to protect.

Onyx2 plastics are incredibly brittle and should be stored in air conditioned, climate controlled storage. Do not cheap out on this; it is not worth the unpleasantness of watching 20+ year old plastics crack and shatter.

To lighten the load, removal of the node boards, raster managers and PCI cage is easily done. With removal of the front skin, it is also possible to remove the fan tray and PSU. The front skin is held on by a single screw in the bottom grille and a number of clips and slides DOWNWARD.

=== Origin 2000 ===
For moving Origin 2000 and Onyx2 racks, 80 inches of clearance are needed, either vertically or horizontally, plus 40x26 for the lateral dimensions of the crack. It is best, due to the fact they can weigh more than 800lbs, to unrack the units and move them individually, but this is not always possible.

Care should be had in removing the plastics for transport.</text>
    <sha1>93ab57c73ecf482618584322396248be9046440c</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Gentoo Prefix-Portage for IRIX</title>
  <ns>0</ns>
  <id>36</id>
  <revision>
    <id>44</id>
    <timestamp>2025-02-05T19:12:32Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "On Nekochan in 2009, user Stuart posted that he had gotten Gentoo Prefix, a type of Portage port to other systems, working on IRIX. This article is an archive/documentation of that effort. Due to the 12-year gap from the time of writing this adaptation of his methods, this article is posted without warranty or guarantees.  === History === Stuart posted on his initial post that he had quit working on pkgsrc (a NetBSD project) for the following reasons:  * The build proces..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8282" xml:space="preserve">On Nekochan in 2009, user Stuart posted that he had gotten Gentoo Prefix, a type of Portage port to other systems, working on IRIX. This article is an archive/documentation of that effort. Due to the 12-year gap from the time of writing this adaptation of his methods, this article is posted without warranty or guarantees.

=== History ===
Stuart posted on his initial post that he had quit working on pkgsrc (a NetBSD project) for the following reasons:

* The build process was too basic and couldn't handle individual upgrades of packages.
* Inattention from the development staff to patch their projects.

In contrast he found ebuilds from Gentoo easy to modify and support staff incredibly helpful. All in all he found this a better way forward.

=== Bootstrapping ===
Firstly, one must decide a prefix. For the purposes of this guide, &lt;code&gt;/opt/gentoo&lt;/code&gt; will be used.

Create this directory, and subdirectory named 'home' within it. Create the user and group 'portage:portage' with UID and GID 250 with the recently-created 'home' directory as their home directory, and then recursively change ownership of the top-level installation directory to 'portage:portage'.

Save the following script as '~portage/.bashrc', altering EPREFIX as necessary:&lt;pre&gt;
EPREFIX="/opt/gentoo"

CHOST="mips-sgi-irix6.5"

PATH="${EPREFIX}/sbin:${EPREFIX}/usr/sbin:\

${EPREFIX}/usr/${CHOST}/bin:\

${EPREFIX}/usr/bin:${EPREFIX}/bin:\

/opt/bin:/usr/local/bin:\

/usr/nekoware/bin:/usr/bsd/bin:\

/usr/nekoware/sbin:/usr/bsd/sbin:$PATH"

export PATH EPREFIX CHOST

LD_LIBRARYN32_PATH="${EPREFIX}/usr/lib:${EPREFIX}/lib:${EPREFIX}/usr/lib/nspr"

export LD_LIBRARYN32_PATH

# This breaks most builds...

#ac_cv_path_RAWCPP="$( which cpp )"

CC="cc"

BUILD_CC="cc"

CXX="CC"

CXXCPP="CC -E"

export CC BUILD_CC CXX CXXCPP # ac_cv_path_RAWCPP

MIPSPRO_DEBUG=0

MIPSPRO_VERBOSE=0

MIPSPRO_PERMISSIVE=0

export MIPSPRO_DEBUG MIPSPRO_VERBOSE MIPSPRO_PERMISSIVE

# This should now all be handled by the IRIX MIPSpro wrapper...

# ... but some builds (such as perl) interrogate these flags directly without

# going via the compiler, so we do need to define them in the environment

# regardless.

common="-O2 -n32 -mips4 -r14000 -float_const -use_readonly_const -TARG:isa=mips4:platform=ip30:processor=r14000 -TENV:zeroinit_in_bss=ON -OPT:fast_io=ON:Olimit=8192:reorg_common=ON:swp=ON -LNO:auto_dist=ON:fusion_peeling_limit=8:gather_scatter=2"

# cc-1035 is generated when the compiler hits '#error', but by default it

# is treated only as a warning. This is broken.

common="$common -diag_error 1035"

# There are various problems building C++ code with MIPSpro 7.4.4m compiler

# front-end, which can actually produce incorrect code. This can be worked-

# around by using the 7.4.3m front-end, which appears not to be affected.

fixcxx="-LANG:std=off:libc_in_namespace_std=off -Zf,_245"

# Comment out the following line to increase C++ compatibility...

unset fixcxx

bsdcompat="-D_BSD_COMPAT"

bsdfull="-D_BSD_TYPES -D_BSD_TIME" # -D_BSD_SIGNALS : Breaks use of &lt;sigaction.h&gt;

quiet="-woff 1174,1183,1185,1552"

ccquiet="${quiet},3968,3970"

# With `-Zf,_245', the higher error numbers aren't set...

if [ -n "$( echo "${fixcxx}" | grep "_245" )" ]; then

cxxquiet="${quiet}"

else

cxxquiet="${ccquiet}"

fi

nowarn="-woff 1009,1014,1110,1116,1188,1204,1230,1233 -Wl,-woff,84,-woff,85"

# Additional options:

# -signed Make variables of type 'char' default to 'signed char' rather than

# 'unsigned char'

#

CPPFLAGS="${BSDCOMPAT} -I${EPREFIX}/usr/include"

CFLAGS="-c99 ${common} ${ccquiet}"

CXXFLAGS="-J2 ${common} -FE:eliminate_duplicate_inline_copies:template_in_elf_section ${cxxquiet} ${fixcxx}"

LDFLAGS="-Wl,-s,-x,-n32,-mips4,-rdata_shared,-allow_jump_at_eop" # -v

LDFLAGS="${LDFLAGS},-rpath,${EPREFIX}/usr/lib:${EPREFIX}/lib -L${EPREFIX}/usr/lib -L${EPREFIX}/lib"

unset common fixcxx bsdcompat bsdfull quiet ccquiet cxxquiet nowarn

export CPPFLAGS CFLAGS CXXFLAGS LDFLAGS

# Other random fixes...

CONFIG_SHELL="$( which bash )"

export CONFIG_SHELL

gentoopath="${EPREFIX}/usr/share/man:${EPREFIX}/usr/man"

sysman="/usr/catman:/usr/share/man:/usr/share/catman"

optman="/opt/man:/opt/modules/2.2.2.5/man"

sgiman="/usr/freeware/catman:/var/sgi_apache/server/man"

localman="/usr/local/man"

bsdman="/usr/bsd/catman:/usr/bsd/man:/usr/bsd/lib/perl5/man:/usr/bsd/lib/perl5/site_perl/man:/usr/bsd/lib/perl5/vendor_perl/man"

nekoman="/usr/nekoware/man:/usr/nekoware/ssl/man"

MANPATH="$gentoopath:$sysman:$optman:$sgiman:$localman:$bsdman:$nekoman"

#MANFMTCMD="groff -Tascii -man"

export MANPATH # MANFMTCMD

unset gentoopath sysman optman sgiman localman bsdman nekoman

# The 'rs', 'hl' and 'ca' directives don't work as of coreutils-7.1

type -pf dircolors &gt;/dev/null &amp;&amp; eval $( dircolors -b | sed 's/rs=[^:]\+:// ; s/:hl=[^:]\+:/:/ ; s/:ca=[^:]\+:/:/' )

alias ls='ls --color=auto -hF'

alias grep='grep --colour'

alias man='PAGER="less" man'

EDITOR="vim"

export EDITOR

XDG_DATA_HOME=/opt/gentoo/usr/share

XDG_DATA_DIRS=/opt/gentoo/usr/share

export XDG_DATA_HOME XDG_DATA_DIRS

# set vi:nowrap
&lt;/pre&gt;Finally, download the bootstrap script from &lt;nowiki&gt;https://gitweb.gentoo.org/repo/proj/prefix.git/plain/scripts/bootstrap-bash.sh&lt;/nowiki&gt; and the compiler wrapper from &lt;nowiki&gt;http://nekofiles.irixnet.org/stuart-contrib/portage-prefix/irixmipsprowrapper.tar.gz&lt;/nowiki&gt;.

Switch to the portage user with su -, copy the bootstrap script to the ~ directory of portage. Extract the compiler wrapper to /opt/gentoo and then run hash -r. From then on the compiler wrappers will be active. These are controlled by the MIPSPRO_ * variables — MIPSPRO_VERBOSE=1 will result in copious output regarding what the wrapper is doing, and MIPSPRO_DEBUG=1 will show additional debugging information. Additional options are MIPSPRO_WRAPPER (set to 0 to disable the wrapper entirely, which is highly unrecommended!), MIPSPRO_ALLOWNOSTD (to allow -nostdlib and -nostdinc, which generally break builds: default off), MIPSPRO_MANGLE (to add additional optimizations beyond simply setting library paths: default on), MIPSPRO_INJECT (experimental fix for use of GNU attributes: default off), MIPSPRO_PERMISSIVE (to pass unrecognised options to the compiler even though they're likely GNUisms: default on for now), and MIPSPRO_ABORT (when MIPSPRO_PERMISSIVE is set to 0, the wrapper exits with a failure if an unrecognised option is encountered, rather than silently dropping it: default off).

By default the wrapper will automatically detect the platform and target and apply other optimisation options, the defaults are: '-mips4', '-n32', and '-O2' with an Olimit of 8192. These can be overridden with MIPSPRO_ISA, MIPSPRO_ABI, OLIMIT, and MIPSPRO_OPT.

Next, run:&lt;pre&gt;
$ chmod 755 bootstrap-prefix.sh

$ STDPATH="$PATH"

$ export PATH="$EPREFIX/tmp/usr/bin:$EPREFIX/tmp/bin:$PATH"

$ ./bootstrap-prefix.sh $EPREFIX tree

There is a flag-o-matic.eclass.patch which may need application here.

$ ./bootstrap-prefix.sh $EPREFIX/tmp make

$ ./bootstrap-prefix.sh $EPREFIX/tmp wget

$ ./bootstrap-prefix.sh $EPREFIX/tmp sed

$ ./bootstrap-prefix.sh $EPREFIX/tmp python

$ ./bootstrap-prefix.sh $EPREFIX/tmp coreutils6

$ ./bootstrap-prefix.sh $EPREFIX/tmp findutils

$ ./bootstrap-prefix.sh $EPREFIX/tmp tar15

$ ./bootstrap-prefix.sh $EPREFIX/tmp patch9

$ ./bootstrap-prefix.sh $EPREFIX/tmp grep

$ ./bootstrap-prefix.sh $EPREFIX/tmp gawk

$ ./bootstrap-prefix.sh $EPREFIX/tmp bash

$ ./bootstrap-prefix.sh $EPREFIX portage

$ hash -r

$ USE="-*" emerge keep-going sed wget bash baselayout-prefix lzma-utils m4 flex bison coreutils findutils tar grep patch gawk make

$ USE="-*" emerge nodeps file

$ FEATURES="-collision-protect" emerge -v --oneshot portage

$ export PATH="$STDPATH"

$ unset STDPATH

$ hash -r

$ rm -r $EPREFIX/tmp/*

$ emerge --sync

$ emerge -uv system

$ emerge -Dev --with-bdeps y system
&lt;/pre&gt;This will result in a minimal working install system.

Finally, add &lt;code&gt;/opt/portage/usr/bin:/opt/portage/bin&lt;/code&gt; to PATH for this to work.

=== Warning ===
As this article derives from things more than 10 years ago, there is no guarantee it'll work.

=== Citations ===

* &lt;nowiki&gt;http://archive.irixnet.org/apocrypha/nekonomicon/forum/15/16720597/1.html&lt;/nowiki&gt;</text>
    <sha1>1a05e6fc5513bbff7569f78fcb99ac8ac853ef6c</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Indigo2-mag.jpg</title>
  <ns>6</ns>
  <id>37</id>
  <revision>
    <id>45</id>
    <timestamp>2025-02-07T02:52:42Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24" xml:space="preserve">IRIS Indigo with monitor</text>
    <sha1>f0b81f1a8f0f8669c49612a41069f20ab7949bf8</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Indigo-front-1000.jpg</title>
  <ns>6</ns>
  <id>38</id>
  <revision>
    <id>46</id>
    <timestamp>2025-02-07T02:53:42Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11" xml:space="preserve">IRIS Indigo</text>
    <sha1>a813758f2f659828947278bd27d59ba05698207a</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>IRIS Indigo</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>47</id>
    <timestamp>2025-02-07T02:54:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial Commit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5557" xml:space="preserve">The SGI Indigo (Also known widely as the IRIS Indigo) is a line of high end workstations using the MIPS processor family released as a successor to the Personal IRIS series.

The Indigo R4000 was also the first SGI workstation that that featured the 64bit R4000 RISC CPU on the desktop, the first SGI in general using the new CPU was the Crimson. The Indigo offers builtin audio capabilities and comes in a very well designed and space efficient chassis. With one of the Express graphics options it offers accelerated 3D graphics.
[[File:Indigo2-mag.jpg|thumb|IRIS Indigo owned by CB_HK]]

=== Features ===

* One 32-bit R3000 at 33MHz or a R4000 at 100MHz, or a R4400 at 150MHz.
* A maximum of 96MB RAM on R3000 boards (IP12), and 384MB on R4x00 boards (IP20)
* Two GIO32 slots for expansion boards.
* A Motorola 56000 DSP-driven Audio system.
* Seven different graphics options:

* Entry (LG1/2 board)
* Express (XS8, XS24, XS24Z, XZ, Elan)

=== Peripherals ===
The Indigo, unlike later SGIs, does NOT possess support for PS/2 and uses the same keyboard as the SGI Onyx and Crimson. To use PS/2 peripherals necessitates an adapter.

The graphics board uses the 13w3 connector which requires a SOG compliant monitor.

=== Storage ===
All Indigo systems have three drive bays for internal 3.5" SCSI devices that have to be mounted on special drive sleds to be used in the systems. The upper two of them can be accessed from the outside through a small door which makes them usable for removable media drives. To remove any of the three drives the front plate has to be removed which is impossible if the system is secured with the locking bar.

The skins of the Indigo are colored in a dark blue which has a decent hint of purple to it. On R3000 Indigos the type of the graphics option the machine was shipped with was printed on the front door. On R4000 a small badge was used that in addition to the name of the graphics option included "4000" to denote the faster CPU type.

=== Operating System Support ===
The Indigo when first introduced was based on the R3000 microprocessor. Support for this system was added to 4D1-4.x from beginning on (4D1-4.0). Support for Elan, XZ and XS graphics was added shortly thereafter in 4D1-4.0.2. Next support for the new R4000 based model was added in 4D1-4.0.5E.

General support for the Indigo can be found in the all platform releases of IRIX 5.x. Only the R4000 models were supported by IRIX 6.2 and IRIX 6.5. The support for the remaining legacy systems like the Indigo R4000 was dropped after 6.5.22 making IRIX 6.5.22 the last version to support any of these systems.
[[File:Indigo-front-1000.jpg|thumb|IRIS Indigo from the front]]

=== Hardware Problems ===
The Indigo does have a number of potential failures:

==== Battery Failure ====
Signs of failure: The system fails to boot and repeats the message "Can't set tod clock"

This error is very common these days and it occurs during boot time. It usually means that the onboard battery is empty and that the system can't set it's clock. It is not fatal and some systems even recover when they are run for a while. This error does not occur while the system is running.

The original battery used is a Tadiran TL-5186 3.6V battery. Current replacements are the Sonnenschein SL-340 or SL-840. Both can be installed in the same place as the original battery of the Indigo.

In the long run a cheaper solution is to wire a socket for a generic button cell to the battery connectors on the main board. The socket could be fixed on one of the GIO32 bus placeholders. The Indigo will work just fine with a standard and much cheaper 3 V button cell (like a CR2032).

==== Memory Controller ====
Signs of failure: While booting the system displays a message like "Warning: Revision C Memory Controller (MC) chip needed in order to properly operate with SIMMS of this type."

When upgrading memory on an R4000 Indigo IRIX might issue the above warning if there is no Rev C memory controller installed in the system (This can be checked using /usr/gfx/gfxinfo). If all memory is detected (i.e. shown in hinv) and there are not unusual problems with the system since the upgrade it should be safe to ignore the message. It was added when there were bugs in some memory modules. The upgraded Rev C memory controller contains a workaround for these bugs, but as these have also long been fixed there should be no problems today - even with older MCs.

In later IRIX the warning message has been worded differently: "WARNING: You may need a memory controller revision C because of the type of simms installed. If you don't experience any memory errors you won't need MC revision C"

==== Bad eaddr ====
Signs of failure: The system complains about a bad ethernet address (ff:ff:ff:ff:ff:ff).

In general this means that the EEPROM that contains the hardware ethernet address is dead or contains invalid data. It is an 8 pin MiniDIP serial EEPROM (93C56) which is socketed on the backplane.

In many cases the reason is, that in the Indigo different CPU boards (IP20, then IP12) were used. The location of the address is different between the two boards and is properly relocated when a system is upgraded from IP12 to IP20. When the IP12 is placed back in the system the MAC address is erased.

A possible solution is to place the IP12 in the system and reset the mac address from the PROM monitor using the eaddr command - the IP20 doesn't allow that. After that the system can be used with the IP12 board or upgraded to IP20 which will relocate the address once again.</text>
    <sha1>e58ddcf9e2b1d812706b38186726b6d45df6dcce</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Crimson-jurassic-classic.jpg</title>
  <ns>6</ns>
  <id>40</id>
  <revision>
    <id>48</id>
    <timestamp>2025-02-07T02:59:06Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">A Jurassic Classic</text>
    <sha1>464aace06a8b9797a65a710904ec8d87ca7c99a5</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:IRIS Crimson.jpg</title>
  <ns>6</ns>
  <id>41</id>
  <revision>
    <id>49</id>
    <timestamp>2025-02-07T03:08:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22" xml:space="preserve">A typical IRIS Crimson</text>
    <sha1>6d00dbe5ba3aab2b067a030c86acf2607aa2ff45</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Crimson</title>
  <ns>0</ns>
  <id>42</id>
  <revision>
    <id>50</id>
    <timestamp>2025-02-07T03:09:09Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The IRIS Crimson or simply Crimson is the successor to the Power Series, first released in 1992. It was the first SGI workstation released with a 64-bit processor. [[File:IRIS Crimson.jpg|thumb|A typical IRIS Crimson]] The Crimson was a member of Silicon Graphics' IRIS 4D series of deskside systems; it was also known as the 4D/510 workstation. It was similar to other SGI IRIS 4D deskside workstations, and could utilize a wide range of graphics options (up to RealityEngin..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5105" xml:space="preserve">The IRIS Crimson or simply Crimson is the successor to the Power Series, first released in 1992. It was the first SGI workstation released with a 64-bit processor.
[[File:IRIS Crimson.jpg|thumb|A typical IRIS Crimson]]
The Crimson was a member of Silicon Graphics' IRIS 4D series of deskside systems; it was also known as the 4D/510 workstation. It was similar to other SGI IRIS 4D deskside workstations, and could utilize a wide range of graphics options (up to RealityEngine). It was also available as a file server with no graphics. 

=== Features ===

* One superpipelined MIPS 100 MHz R4000 or 150 MHz R4400 processor.
* Seven high performance 3D graphics subsystem options deliver performance and features to match any application.
* Up to 256 MB memory and internal disk capacity up to 7.2 GB, expandable to greater than 72 GB using additional enclosures.
* High performance I/O subsystem includes four VME expansion slots, Ethernet and two SCSI channels with disk striping support.
* Seven graphics configurations:

* S, no display, server only
* Entry (LG1/2 board) with VME adaptor*
* Express with VME adaptor*
* ELAN with VME adaptor*
* "Clover2": GTX and GTX(B) boardset
* "Powervision": VGX and VGXT boardset
* "Venice": RealityEngine boardset

&lt;nowiki&gt;*&lt;/nowiki&gt;These boards are identical to the IRIS Indigo

=== Notes ===
The memory modules used in the Crimson are the same as on the MC2 memory board used by the Power Series. However, unlike other IRIS 4D series machines an MC2 board is not recognized by the system. All memory (up to 256MB) must be installed on the IP17 mainboard.

The minimal system configuration consists of two cards: IP17 (CPU mainboard) and IO3B (Input/Output mainboard)

While the MIPS R4000 is a 64-bit processor, the Crimson is only capable of running it in 32-bit mode.

IRIS Crimson can operate with IRIX 6.2, but there are bugs in fx.IP17 in the IRIX 6.2 release. In order to prepare a drive you will either need an earlier version of fx, or you must run fx on another system to partition the drive first.

=== Components ===

==== IP17 ====
The CPU mainboard supports either a 100MHz R4000 or 150MHz R4400 CPU with 1MB L2 memory cache and the memory sub-system.

The bus frequency is half of the core speed, either 50MHz or 75MHz depending on the CPU installed.

The differences between the two versions include the PROM revision and different logic on the board.

The Crimson does not support an MC2 board, any memory up to the maximum amount of 256MB must be installed on the IP17 board.

The Crimson supports only one IP17 board unlike its successor, the rackmount Onyx, which supports multiple CPU boards depending on configuration (the deskside Onyx only supports one CPU mainboard but with multiple processors)

==== I03B ====
The Input/Output mainboard supports the following:

* 2 SCSI channels driven with Western Digital 33C93--one internal device connection and one external device connection
* 2 Centronics connectors on the chassis
* 4 serial ports
* 1 parallel port
* 1 AUI 10Mb ethernet port
* 3 powered peripheral ports (8 Pin DIN)

==== Graphics Subsystems ====
The Crimson could be outfitted with seven different graphics setups depending on the end-user's desired needs. Users seeking a file server could opt for no graphics option, which would mean relying on a terminal or network connection to manage the system as there is no basic graphics capability built into the IP17 or IO3B boards. The six other options consisted of varying levels of performance, ranging from Entry graphics, all the way to RealityEngine. These graphics systems were independent of the IP17 and IO3B boards and could be swapped out in order to provide more or less capability as required.

=== Y2k Bug ===
As the IRIS Crimson had already been replaced by the Onyx and Onyx2 prior to the year 2000, little to no work was done to patch the system prior to the turn of the millennium. While the Crimson is not Y2K proof, the error it encounters is not fatal and can easily be rectified by adding a daemon to startup that will sync the time via NTP and reset the Crimson's internal clock. Failure to re-sync the time will cause the system to gain at least one year each time it is restarted until it reaches the end of the Unix epoch at which time it will cycle back. This has the potential for corrupting files and causing licenses to expire prematurely.
[[File:Crimson-jurassic-classic.jpg|thumb|A "Jurassic Classic" Crimson]]

=== In Popular Culture ===
An IRIS Crimson appeared in the main operations center of Jurassic Park. During one scene in the film, the granddaughter of the park's creator, Lex, used the machine to navigate the filesystem of IRIX 4.0 using the application FSN in order to reactivate the locks on the operations center doors. The increase in popularity of the Crimson following the release of the movie prompted Silicon Graphics to release a special edition model referred to as the "Jurassic Classic." It was notable for being marked as such on the outside of the case, in addition to being signed by Silicon Graphics founder Jim Clark.</text>
    <sha1>19f8bde2c5cb0c0f1f599a8b7dcb36abc06b06fb</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>File:Indymag.jpg</title>
  <ns>6</ns>
  <id>43</id>
  <revision>
    <id>51</id>
    <timestamp>2025-02-07T03:11:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">Indy owned by CB_HK</text>
    <sha1>0a2d5c68a98b95a87b25c5a7bd11d30e6b341f1c</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Indy</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>52</id>
    <timestamp>2025-02-07T03:12:00Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Indymag.jpg|thumb|500x500px|SGI Indy owned by CB_HK]] The Indy, code-named "Guinness", is one of the low-end workstations by Silicon Graphics. Selling for around $5000 USD at base price it was one of the cheaper models. It is notable for its common-ness, comparable to the Amiga 500 for Amigas, and its use in development for the Nintendo 64. It was introduced on July 12, 1993 and discontinued on June 30, 1997.  === Features === The Indy is a small desktop (dimensio..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7026" xml:space="preserve">[[File:Indymag.jpg|thumb|500x500px|SGI Indy owned by CB_HK]]
The Indy, code-named "Guinness", is one of the low-end workstations by Silicon Graphics. Selling for around $5000 USD at base price it was one of the cheaper models. It is notable for its common-ness, comparable to the Amiga 500 for Amigas, and its use in development for the Nintendo 64. It was introduced on July 12, 1993 and discontinued on June 30, 1997.

=== Features ===
The Indy is a small desktop (dimensions 41 x 36 x 8 centimetres) computer consisting of a steel frame with a removable bright blue plastic skin. The system is capable of supporting the weight of a small CRT or a modern LCD/LED monitor without damage.

After removing the plastic skin, the power supply, long, thin and bolted to the side of the computer is visible, along with the motherboard, any 3.5" hard disks or the optional Floptical drive, along with the GIO riser and video card, as well as both expansion ports.

==== CPU ====
The processors are supplied on a "Processor Module" board with or without external cache (Primary Cache means no external cache, Secondary Cache means there is an external cache) and range from a 100MHz R4000 to a 180MHz R5000.

Indy's motherboard has a socket for the Processor Module (PM). Early Indys used the 100 MHz MIPS R4000 CPU, which quickly proved inadequate. The Indy, at the bottom of SGI's price list, thus became the primary platform for MIPS's low-cost, low-power-consumption R4600 CPU series. The R4600 had impressive integer performance, but had poor floating-point capability. This, however, wasn't too huge of a problem in a box that was generally not designed for floating-point-intensive applications. For this reason, the R4600 made an appearance outside the Indy line just once, and only briefly, in the Indigo 2. This series of CPU issues, along with the relatively low-powered graphics boards, lower maximum RAM amount, and relative lack of internal expansion ability compared to the Indigo led to the Indy being pejoratively described amongst industry insiders as "An Indigo without the 'go'."

The R4600 chip itself has no L2 cache controller, external controller was used to add 512K of L2 cache. R4600s processor modules both with an L2 cache (SC) and without (PC) are common in the Indy. At the same clock rate, the SC version of the processor module is generally 20 to 40 percent faster than the PC version, due to the memory cache.

The Indy was also the first SGI to utilize the MIPS R5000 CPU, which offered significant advantages over the R4400 and R4600 it replaced. The Indy's 180 MHz R5000 module can be overclocked to 200 MHz by replacing its crystal oscillator chip.

==== Memory ====
The system takes standard 72-pin SIMMS (gold plated SIMMS are recommended to avoid dielectric corrosion) and can take anywhere from as low as 16MB to 256MB, these must be added in sets of 4 at a time since the computer is 64-bits and each SIMM is a 16-bit module.Upon release, the base configuration came at 16MB. IRIX 5.1, the first Operating System for the Indy, did not take full advantage of the hardware due to inadequate memory management and the 16MB configuration failed to even boot. SGI quickly increased the base specification to 32 MB, and shipped free memory upgrades at considerable cost. Subsequent IRIX releases made huge improvements in memory usage.

==== Graphics ====
Graphics are one of three possible types: 8-bit XL, 24-bit XL, and XZ. The 24-bit XL card is the most desirable for collectors due to its decent 2D performance and better than the XZ 3D performance when combined with an R5000 CPU. All three options use the 13W3 connector and require a Sync on Green monitor.

The Indy includes analog and digital video inputs, such as Composite and S-Video, as well as a proprietary digital D-sub used by the Indycam. The system is capable of capturing video at a maximum resolution of either 480i or 576i, depending on region.

It takes a fast machine to capture at either of these resolutions, though; an Indy with slower R4600PC CPU, for example, may require the input resolution to be reduced before storage or processing. However, the Vino hardware is capable of DMAing video fields directly into the framebuffer with minimal CPU overhead.

None of the Indys support video output by default - that would require the Indy Video GIO32 card. In addition, there is an optional video module called CosmoCompress, which offers realtime JPEG video compression and decompression and uses up another GIO32 slot.

==== Networking ====
For networking, the Indy has an on-board AUI, an ISDN port, and a 10Mb Ethernet jack. The AUI and Ethernet cannot be used at the same time, the Ethernet jack takes priority automatically. 10/100Mb cards are available on the used market for faster connection speeds.

==== Storage ====
The Indy has two drive bays for 1-inch tall 3.5" drives. The upper drive bay is externally accessible and may hold a SCSI floptical drive. All external and internal drives share a single Fast SCSI bus (unless a GIO32 SCSI card has been installed). External CD-ROM drive connect via SCSI connector at rear side of the box. Typical drive supports boot, OS install, audio. Special ROM is required to boot from for certain device types.

=== Operating System Support ===
The Indy's basic support came in IRIX 5.1 but that is not a recommended release. The Indy is supported through IRIX 6.5.22, it is recommended to use one of the following releases:

* IRIX 5.3
* IRIX 6.2
* IRIX 6.5.22

IRIX 6.5.22 has the most software available, but will be slow on systems below 128MB. 6.2 and 5.3 are much lighter weight, but have their own limitations.

=== Hardware Problems ===
The component of the Indy most prone to failure is the power supply. Neither the Sony nor the Nidec varieties are more reliable, and both have benefits and drawbacks.

==== MAC/System Serial ====
The Indy's Ethernet address, which doubles as the system's serial number, is stored in battery-backed RAM. This means that when the internal battery dies, so does the system - it will hang at the PROM monitor and refuse to boot any further as a result of the Ethernet address being all FFs. A non-amateur user can replace the PROM battery and reprogramme it. The original battery was made by Dallas Semiconductor, now owned by MAXIM. The original unit was marked the "DS-1386-8K-150", however its replacement unit, the "DS-1386-8K-120" can be directly substituted with no ill effects.

To reset the MAC, it's necessary to use fill commands:

To set the MAC 08:00:69:08:e2:0a, for example, this would be done from the PROM:&lt;pre&gt;
fill -w -v 0x08 0xbfbe04e8

fill -w -v 0x00 0xbfbe04ec

fill -w -v 0x69 0xbfbe04f0

fill -w -v 0x08 0xbfbe04f4

fill -w -v 0xe2 0xbfbe04f8

fill -w -v 0x0a 0xbfbe04fc
&lt;/pre&gt;The MAC address is (usually) on a sticker to the rear of the unit, and hence can be reprogrammed without losing software licenses, which often rely on it to verify ownership. Otherwise, any MAC address in SGI's block is usable.</text>
    <sha1>6c4b048ce13deda5341a14a4ed091ee395df3389</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Challenge S</title>
  <ns>0</ns>
  <id>45</id>
  <revision>
    <id>53</id>
    <timestamp>2025-02-07T03:20:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The Challenge S is the server variant of the Indy workstation, utilizing the same basic hardware. It has some minor differences that make it different from the Indy in terms of hardware support, but is structurally similar.  === Features === The Challenge S is a small desktop (dimensions 41 x 36 x 8 centimetres) server with a slightly darker case compared to the Indy. Inside the hardware is nearly identical: power supplies; processor modules; hard disks; memory; and GIO3..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2579" xml:space="preserve">The Challenge S is the server variant of the Indy workstation, utilizing the same basic hardware. It has some minor differences that make it different from the Indy in terms of hardware support, but is structurally similar.

=== Features ===
The Challenge S is a small desktop (dimensions 41 x 36 x 8 centimetres) server with a slightly darker case compared to the Indy. Inside the hardware is nearly identical: power supplies; processor modules; hard disks; memory; and GIO32 cards are all interchangeable between the systems. On the rear, the Challenge S lacks video input/output, PS/2 ports and the RJ11 Ethernet port. All of this necessitates using the AUI connector or the mezzanine NIC (which doesn't work in the PROM) for connectivity.

==== CPU ====
The processors are supplied on the same processor modules used on the Indy and are otherwise identical.

=== Memory ===
The system takes standard 72-pin SIMMS (gold plated SIMMS are recommended to avoid dielectric corrosion) and can take anywhere from as low as 16MB to 256MB, these must be added in sets of 4 at a time since the computer is 64-bits and each SIMM is a 16-bit module.

=== Graphics ===
The Challenge S cannot accept any graphics hardware.

=== Networking ===
For networking, the Challenge S has an on-board AUI and an ISDN port, the ethernet twisted pair/rj11 jack was omitted presumably for cost reasons. 10/100Mb cards are available on the used market for faster connection speeds.

==== Storage ====
The Challenge S has two drive bays for 1-inch tall 3.5" drives. The upper drive bay is externally accessible and may hold a SCSI floptical drive. All external and internal drives share a single Fast SCSI bus (unless a GIO32 SCSI card has been installed). External CD-ROM drive connect via SCSI connector at rear side of the box. Typical drive supports boot, OS install, audio. Special ROM is required to boot from for certain device types.

=== Operating System Support ===
The Challenge S' basic support came in IRIX 5.1 but that is not a recommended release. It is supported through IRIX 6.5.22, it is recommended to use one of the following releases:

* IRIX 5.3
* IRIX 6.2
* IRIX 6.5.22

IRIX 6.5.22 has the most software available, but will be slow on systems below 128MB. 6.2 and 5.3 are much lighter weight, but have their own limitations.

=== Hardware Problems ===
The component of the Challenge S most prone to failure is the power supply. Neither the Sony nor the Nidec varieties are more reliable, and both have benefits and drawbacks in power factor, cooling and cleanliness of the output.</text>
    <sha1>fdda5bbf4b3daad6ac515b0632b0b1a935549de0</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Indigo2-purple.jpg</title>
  <ns>6</ns>
  <id>46</id>
  <revision>
    <id>54</id>
    <timestamp>2025-02-07T03:22:34Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24" xml:space="preserve">An R10000 Indigo2 Impact</text>
    <sha1>c9078fbd0d1bf43f6e2b3c109a21422361620205</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Indigo2</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>55</id>
    <timestamp>2025-02-07T03:57:07Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The Indigo 2, codenamed "Fullhouse" is a high end workstation marketed by Silicon Graphics from 1993 to 1997, with production of IMPACT models ending in 1998. The Indigo 2 succeeded the earlier IRIS Indigo line and is the higher end version of the Indy.  === Features === The Indigo 2 is a large teal or purple desktop that is deceptively heavy, around 40lbs. It came with two plastic feet which can be used to set it upright vertically.  ==== CPU ==== The Indigo 2 has three..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4505" xml:space="preserve">The Indigo 2, codenamed "Fullhouse" is a high end workstation marketed by Silicon Graphics from 1993 to 1997, with production of IMPACT models ending in 1998. The Indigo 2 succeeded the earlier IRIS Indigo line and is the higher end version of the Indy.

=== Features ===
The Indigo 2 is a large teal or purple desktop that is deceptively heavy, around 40lbs. It came with two plastic feet which can be used to set it upright vertically.

==== CPU ====
The Indigo 2 has three distinct variants, each with a specific motherboard and "IP" number or designation:

* IP22 supports an R4000, R4400, or R4600 CPU clocked at 100-250MHz
* IP26 supports the R8000 CPU clocked at 75MHz
* IP28 supports the R10000 CPU clocked at either 175 or 195MHz

IP26 systems were generally referred to as the POWER Indigo 2, while the IP28 systems usually had a grill badge that read "10000."
[[File:Indigo2-purple.jpg|left|thumb|Indigo2 Impact with an R10000]]

==== Memory ====
All three variants had 12 SIMM slots on the motherboard, organized into three banks of four slots each, and took industry standard fast page mode (FPM) 72 pin SIMMs with parity. Speeds should be 60 or 70 nanoseconds, and the internal organization must be 36 bits wide - 8MB x 72 bit parts will not work.

IP22 systems will support up to 384MB with 32MB SIMMs. While the IP26 and IP28 systems both support 64MB SIMMs, published limits for these systems reflected concerns about the amount of heat generated by then-current DRAM chips. According to SGI the R8000-based IP26 systems would only support 640MB (2 banks of 256MB, one of 128MB), while the R10000-based IP28 would support 768MB (3 x 256MB).

Eventually 64MB SIMMs became available that generated less heat, and denser 128MB SIMMs became available. Both the IP26 and IP28 can use these 128MB SIMMs, but with limitations. IP26 systems require some banks to use lower-profile SIMMs to clear the CPU carrier, and SGI described limits on the mix of different density SIMMs in these systems. However owners have reported working configurations of up to 896MB (1 x 128MB, 1 x 256MB, 1 x 512MB bank).

With the IP28 it is possible to achieve a total of 1GB of RAM (2 banks x 512MB, or 2 x 256MB + 1 x 512MB), but unfortunately this appears to be a hard limit based on address logic.

==== Graphics ====
The graphics boards available for the Indigo 2 were the pre-IMPACT Newport and Express boards (which included the SGI XL24, SGI XZ, SGI Elan and SGI Extreme) and the MGRAS IMPACT boards (the SGI Solid IMPACT, the SGI High IMPACT, the SGI High IMPACT AA, and the SGI Maximum IMPACT). IMPACT graphics is not supported by the Power Indigo 2 (R8000 CPU). The Indigo2's replacement, the SGI Octane, offered an upgraded bus but featured the same graphics options, albeit in repackaged form.

The IMPACT units are purple, though it is feasible to upgrade a teal Indigo 2 with proper upgrade parts.An IMPACT-ready Indigo 2 must have an IMPACT-ready riser card, an IMPACT-ready power supply, and a sufficiently recent PROM revision.

==== Networking ====
For networking, the Indigo 2 has an on-board AUI and a 10Mb Ethernet jack. The AUI and Ethernet cannot be used at the same time, the Ethernet jack takes priority automatically. 10/100Mb cards are available on the used market for faster connection speeds. This is near identical to the Indy's configuration.

==== Storage ====
The internal drive bays of the Indigo2 take model-specific carriers. These carriers mate to a backplane using a non-standard connector, and contain devices using a standard 50 pin IDC ribbon cable connector. There may not be enough room in the carrier to use an adapter board to use 68 or 80 pin devices unless using a down-sized device, e.g. a 2.5" hard drive in a 3.5" drive carrier.

=== Operating System Support ===
The first Indigo 2 systems were introduced during the 4D1-4.x era. These were based on the R4000 microprocessor and featured Express graphics (Elan, XZ). Support for new hardware was added in future releases during this period and later on in the 4D1-5.x era.

Major milestones include the introduction of the Impact graphics options as well as the step from the R4000 to the R10000 CPU. For Impact graphics special versions of the IRIX 5.3 and IRIX 6.2 release were offered. Similarly a special release of IRIX 6.2 was made for the R10000 CPU upgrade.

General support for all Indigo 2 variants can be found in the all platform IRIX 6.5. The support for the remaining legacy systems like the Indigo 2</text>
    <sha1>bc289f603814700a86279caf75a3e6e32585e212</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Onyx2 with Multichannel.jpg</title>
  <ns>6</ns>
  <id>48</id>
  <revision>
    <id>56</id>
    <timestamp>2025-02-07T04:02:45Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="27" xml:space="preserve">Multichannel display option</text>
    <sha1>ea514c05f90dc3cc913cab17e3c2f321f83d71db</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Onyx-R10k.jpg</title>
  <ns>6</ns>
  <id>49</id>
  <revision>
    <id>57</id>
    <timestamp>2025-02-07T04:03:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9" xml:space="preserve">Onyx-R10k</text>
    <sha1>f4092a500134334ede5ef98f8669aa8aa43fac01</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:940110-Periodic Table.jpg</title>
  <ns>6</ns>
  <id>50</id>
  <revision>
    <id>58</id>
    <timestamp>2025-02-07T04:04:40Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="26" xml:space="preserve">SGI Periodic Table of Onyx</text>
    <sha1>109a35a3c3bdebf521279722fad227d8fd7a544b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Onyx RE2.png</title>
  <ns>6</ns>
  <id>51</id>
  <revision>
    <id>59</id>
    <timestamp>2025-02-07T04:05:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">Reality Engine2 Onyx diagram</text>
    <sha1>47aa63906c89b08ab227a567823499890dee124e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Onyx Infinite Reality Diagram.png</title>
  <ns>6</ns>
  <id>52</id>
  <revision>
    <id>60</id>
    <timestamp>2025-02-07T04:06:44Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">InfiniteReality Onyx Diagram</text>
    <sha1>22c794fe4f75851a4ec0cbe4b1fa14ea73f0b914</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Onyx</title>
  <ns>0</ns>
  <id>53</id>
  <revision>
    <id>61</id>
    <timestamp>2025-02-07T04:07:13Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial Commit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="45569" xml:space="preserve">[[File:Onyx2 with Multichannel.jpg|thumb|Multichannel Display option for an Onyx]]
The Silicon Graphics Onyx (frequently known as the Onyx1 or Original Onyx, or by its form-factor specific codenames Eveready and Terminator) is a graphics supercomputer introduced by Silicon Graphics in 1993 to replace their short-lived Crimson. Also based on the POWERpath-2 Everest architecture, the Onyx is closely related to the Challenge L/XL systems offered by SGI during the same time period, and shares many parts. In general, the difference between an Onyx and a Challenge L/XL is that while the Challenge usually supports more CPUs and memory (with the exception of the Challenge DM), it does not support the installation of a graphics boardset (with the exception of the Challenge GR). The Onyx sat at the high-end of SGI's early-to-mid 1990s product line, above both the Indigo2 and Indy, and was used for tasks such as visualization, simulation, and early virtual reality systems. The system was succeeded on October 7th, 1996 with the launch of the Onyx2. Though production of new Onyxes ended in March of 1999, with the end of service in December of 2008, SGI continued to use the Onyx brand name on their most capable graphics systems until July of 2003, with the introduction of the Onyx4. 

=== Variants and Naming ===
The Onyx is a highly modular system, and was offered in a number of processor and graphics combinations throughout its lifespan. Though some configurations (such as an R8000-based Onyx with VTX graphics) were not offered officially, most CPU/Graphics combinations were, each under a different name. There were ten different, individually named "major variants" of the Onyx. The table below describes these.
{| class="wikitable"
| colspan="6" |Table of officially-offered Onyx Variants
|-
|Variant Name
| colspan="5" |Meaning
|-
|Onyx RealityEngine2
| colspan="5" |An R4000-based Onyx using a RealityEngine2 graphics subsystem
|-
|Onyx VTX
| colspan="5" |An R4000-based Onyx using a VTX graphics subsystem
|-
|Onyx Extreme
| colspan="5" |An R4000-based Onyx using an Extreme Graphics graphics subsystem
|-
|POWER Onyx RealityEngine2
| colspan="5" |An R8000-based Onyx using a RealityEngine2 graphics subsystem
|-
|POWER Onyx Extreme
| colspan="5" |An R8000-based Onyx using an Extreme Graphics graphics subsystem
|-
|Onyx InfiniteReality
| colspan="5" |An R4000-based Onyx using an InfiniteReality graphics subsystem
|-
|Onyx 10000 RealityEngine2
| colspan="5" |An R10000-based Onyx using a RealityEngine2 graphics subsystem
|-
|Onyx 10000 InfiniteReality
| colspan="5" |An R10000-based Onyx using an InfiniteReality graphics subsystem
|-
|Reality Station
| colspan="5" |An R4000 or R10000-based Onyx using a RealityEngine2 graphics subsystem. Limited to only one CPU
|-
|i-Station
| colspan="5" |An R4000 or R10000-based Onyx using an InfiniteReality graphics subsystem. Limited to only one CPU
|-
| colspan="6" |Note: SGI does not appear to have officially offered a POWER Onyx VTX, an Onyx 10000 VTX, or an Onyx 10000 Extreme.
|}
SGI Workstation/Client Periodic Table November 4th, 1994 demonstrates the naming discrepancy between Onyx and POWER Onyx systems with Extreme Graphics installed. While POWER Onyxes are labeled with a slash as POWER Onyx/Extreme, Onyxes are labeled without the slash.
[[File:Onyx-R10k.jpg|left|thumb|R10000 Onyx variant]]
In some cases, such as on their Periodic Tables, SGI also listed the number of processors after the first portion (the one which represents the CPU) of the name. For example, a system with RealityEngine2 graphics and four R4000 CPUs would be an Onyx/4 RealityEngine2, a system with RealityEngine2 graphics and twelve R8000 CPUs is a POWER Onyx/12 RealityEngine2 and so-on. Interestingly, R4000 systems with Extreme graphics do not use the "slash-CPU" notation, meaning that, for example, an system with two R4000s and a system with four R4000s, each with Extreme Graphics, are both known simply as the Onyx Extreme. The same goes for the R8000-based POWER Onyx, except that the slash is kept with only the number removed. All R8000-based Onyxes using Extreme Graphics are known simply as the POWER Onyx/Extreme. This strange phenomenon can be seen on the November 4th, 1994 Workstation/Client Periodic Table (image on right) and the very similar Workstation/Client Periodic Table rev. 2/14/95 (the only difference of which is a change to the aesthetic of the title and the removal of the Crimson RealityEngine and its replacement with the Reality Station, which is, redundantly, known there as the Reality Station RealityEngine2). While this discrepancy between the POWER Onyx and the regular, R4000 Onyx's naming schemes could be mistaken for a typo, its presence on two similar but different revisions of the Periodic Table makes this unlikely.

=== Architecture ===
[[File:940110-Periodic Table.jpg|thumb|SGI Periodic Table]]
The architecture of the SGI Onyx can be roughly divided into two main parts — the POWERpath-2 bus (frequently known as EBus) and the HIO bus (also known as IBus), including the buses and interfaces which interface with the system via it. While the POWERpath-2 bus provides a high-speed interconnect for CPUs, memory, and the I/O subsystem, the HIO bus provides both direct expansion capabilities using the HIO connectors on the IO4, and interfaces to a number of other system components over FCI (via the F Controller ASICs), VMEbus (via the FCI-connected VMECC), SCSI (via the S1IC) and numerous miscellaneous interfaces (via the EPC).
[[File:Onyx RE2.png|left|thumb|Onyx2 RealityEngine2 diagram]]
POWERpath-2 is the successor to SGI's POWERpath architecture, which they had previously used in their PowerSeries and Crimson systems. While it is officially known as POWERpath-2, it is often called EBus, short for "Everest Bus", Everest being the codename for the system architecture shared by the Onyx and Challenge L/XL. While not the "true" name of the bus, the "EBus" moniker is frequently used both by Onyx owners and by SGI themselves (such as on the slot number label affixed below the slots of the Onyx cardcage). The 256-bit POWERpath-2 bus has a data transfer rate of 1.2GB/s (as compared to the 64MB/s of the original POWERpath), and is used exclusively for the system's core components, the IP19/21/25, MC3, and IO4 boards (not for add-on options or graphics boards). POWERpath-2 is unique to Everest systems (Onyx and Challenge L/XL), and was replaced with the S2MP architecture in the later Onyx2 and Origin2000.
[[File:Onyx Infinite Reality Diagram.png|thumb|InfiniteReality Onyx Diagram]]
While core components are connected to POWERpath-2, their interface with the rest of the system is provided by the IO4 board. The IO4 uses an internal 64-bit bus, which, like POWERpath-2, has two names, those being HIO and IBus. When referring to add-on cards connected to the IO4 using it, it is usually referred to as the HIO (high-speed I/O) bus. However, it is also used internally on the IO4, and it seems that the term "IBus" is preferred here. IBus has a bandwidth of 320MB/s, and is shared by HIO add-ons, VME devices and the graphics subsystem (via F Controller ASICs and the VCAM), and the IO4's built-in EPC I/O controller (which, in turn, creates another bus used for basic I/O devices, the 16-bit PBus) and S1IC SCSI controller. VME devices and graphics boards do not connect directly to IBus. Instead, the IO4 also contains two F Controller ASICs, each of which connects to IBus and creates an FCI, or Flat Cable Interface. These two FCI interfaces are exposed on two connectors towards the rear of the IO4. Attached to these connectors (resting on standoffs above the IO4's PCB, much like the HIO options in front of it) is another board known as the VCAM, or VME Channel Adapter Module. The VCAM serves two primary functions, each using one of the FCI interfaces created on the IO4.

As the name of the device states, one of these functions is to act as an adapter between the system and its VME add-on boards. VMEbus is an industry-standard bus developed by Motorola for systems based on their 68000 processor, and used in many systems both with and without the 68000. Though the Everest family were the final SGI systems to use VMEbus, it was far from the first, with many previous SGI systems and add-ons also using it. The Onyx implements VME Revision C, as well as the A64 and D64 modes of Revision D, allowing VME bandwidth up to 60MB/s when DMA is used. The deskside Onyx has 4 VME slots, one of which is filled by the VCAM, while the rack has either four or twelve slots, depending on cardcage configuration (see below for details). The VCAM provides this VME interface using its onboard VMEBus controller chip, and interfaces the VME bus to one of its FCI interfaces using the VMECC (VME Cache Controller).

The other FCI interface provided to the VCAM is simply passed through to the backplane, for use by the graphics subsystem. This is the other primary function of the VCAM. The graphics subsystem communicates with the host system over its FCI interface using its GFXCC (meaning unknown, but probably "Graphics Cache Controller", in the vein of "VME Cache Controller").

In an Onyx Rack, the number of VME slots available depends on whether the system's third cardcage is used. When only two cardcages are used, the rack Onyx has four VME slots, all in Cardcage 2, one of which is filled by the VCAM attached to the IO4. This is the same configuration found in deskside systems. When the third cardcage is used, eight more VME slots, for a total of twelve, are made available. These slots are divided into two groups, found in slots 1, 2, 3, 4 and 12, 13, 14, 15 in Cardcage 3. Slots 1 and 12, the first of each group, contain a VCAM-like board known as an RVCAM, or Remote VCAM, which provides a VME bus to the three slots next to it. No RVCAMs are required if only two cardcages are used, as the VCAM connected to the system's IO4 is sufficient to control the VME slots in Cardcage 2.

In systems equipped with Extreme Graphics, the VCAM is replaced with a GCAM (meaning unknown, but likely "GIO Channel Adapter Module", in the vein of "VME Channel Adapter Module"), effectively replacing the system's VME bus with a GIO64 bus (albeit in a strange form factor). While the exact components of the GCAM are unknown, it likely uses an ASIC in order to interface the GIO bus to one of the FCI interfaces usually used by the VCAM. Assuming the naming scheme for FCI-connected devices was followed, this chip was likely known as the GIOCC. An adapter is then used to install an Indigo2 Extreme Graphics option in a "VME" (the actual protocol is GIO, but the same physical slots on the backplane are used) slot. While both the GCAM and the adapter are relatively unknown and extremely rare, the adapter is especially hard to find details about. It has been mentioned only a few times on Nekochan Forums, with user "whiter" referring to it as "the GIO2VME adapter" in one post and "AB5 (GIO64 to 9u VME shoehorn)" in another, and user "thegoldbug" referring to it as "a small circuit board (SLAG2) with resistors that connects to the VME bus", going on to conclude that "The GCAM must be doing all the work". In a thread about this board created by whiter, another user, "kshuff", says that he owns an Onyx with Extreme Graphics, and that it was factory-installed in his system. The board appears to have been named the AB5 (possible meaning Adapter Board 5), though the names GIO2VME and SLAG2 are also possibilities, and is seemingly smaller than a usual VME-like board, while consisting of "resistors". Based on this, it is likely a small board, the electronics of which consist solely of passives, located at the rear of a VME slot and containing a GIO64 connector of the sort seen in the Indigo2. In order to mount the non-VME-sized Extreme Graphics boardset in the Onyx cardcage, as well as to affix it to the adapter board, some form of carrier, likely a simple metal frame, was probably used. How the Extreme Graphics boardset's ports were moved to the expansion panels in the cardcage door or the graphics bulkhead below is unknown. It has been noted that a spare GCAM and AB5 board could be used with an Extreme Graphics boardset from an Indigo2 in order to add graphics capabilities to a Challenge L/XL, however thegoldbug, one of the owners of this hardware mentioned above, claims to have attempted this configuration twice, using two different AB5 boards, unsuccessfully. The possibility of adding a non-Extreme GIO64 board such as an IMPACT graphics boardset or other Indigo2 card to an Everest system using the GCAM and AB5 has also been raised, however the conclusion seems to be that it would not be possible due to driver problems.

==== CPU ====
The Onyx's CPUs reside on the IP board, which is installed in a POWERpath-2 slot. Though there are 22 different CPU boards available for the Onyx, they are divided into three main categories by their IP number. While most SGI systems spanning multiple processor families use only one IP number (such as the O2, which is an IP32 system regardless of whether an R10000 or R5000 is installed), the IP number of the Onyx and its CPU board(s) is determined by its CPU family. The IP19 board contains one, two, or four R4400 (R4000-family) processors, and was originally the only processor board offered in Onyx systems. With the introduction of the POWER Onyx and the R8000, the IP21 board, containing either one or two R8000s, was released. Note that because there is no IP21 board with four processors, the usual maximum processor count of 4 in desksides and 24 in racks is halved to 2 and 12, respectively. Finally, with the introduction of the Onyx 10000, the R10000-based IP25 board was introduced, which, like the IP19 board, can contain one, two, or four processors.

Desksides allow one IP CPU board, which must be installed in its designated slot (labeled on the sticker below the cardcage). Given the maximum of four CPUs per board, this means the maximum number of CPUs that can be installed in a deskside system is four. Rack systems are significantly more flexible, having eleven EBus slots, five in Cardcage 1 and six in Cardcage 2. Slot 6 in Cardcage 2 must be filled by the master IO4 board, however the ten remaining slots can be used for either IP CPU boards or MC3 memory boards. Additionally, the five remaining EBus slots in Cardcage 2 (those not filled by the mandatory Master IO4 in Slot 6) may be used for additional IO4 boards, though the five slots in Cardcage 1 cannot. Up to six of these slots may be filled with IP boards, allowing up to 24 CPUs in an Onyx rack system.
{| class="wikitable"
| colspan="7" |Table of Onyx IP CPU Boards
|-
|SGI Part No.
|IP No.
|CPUs
|CPU
|Clock
| colspan="2" |Secondary Cache
|-
| colspan="7" |IP19 (R4000):
|-
|030-0642-xxx
|IP19
|1
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0249-00x
|IP19
|2
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0250-0xx
|IP19
|4
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0525-00x
|IP19
|1
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0374-00x
|IP19
|2
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0375-00x
|IP19
|4
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0720-00x
|IP19
|1
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0652-00x
|IP19
|2
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0653-00x
|IP19
|4
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0806-00x
|IP19
|1
|R4400
|250MHz
| colspan="2" |1MB
|-
|030-0805-00x
|IP19
|2
|R4400
|250MHz
| colspan="2" |4MB
|-
|030-0804-00x
|IP19
|4
|R4400
|250MHz
| colspan="2" |4MB
|-
| colspan="7" |IP21 (R8000):
|-
|030-0636-00x
|IP21
|1
|R8000
|75MHz
| colspan="2" |4MB
|-
|030-0625-00x
|IP21
|2
|R8000
|75MHz
| colspan="2" |4MB
|-
|030-0751-00x
|IP21
|1
|R8000
|90MHz
| colspan="2" |4MB
|-
|030-0702-00x
|IP21
|2
|R8000
|90MHz
| colspan="2" |4MB
|-
| colspan="7" |IP25 (R10000):
|-
|013-1672-00x
|IP25
|1
|R10000
|195MHz
| colspan="2" |1MB
|-
|013-1675-00x
|IP25
|1
|R10000
|195MHz
| colspan="2" |2MB
|-
|030-1107-xxx
|IP25
|2
|R10000
|195MHz
| colspan="2" |1MB or 2MB
|-
|030-1107-xxx
|IP25
|4
|R10000
|195MHz
| colspan="2" |1MB or 2MB
|-
|030-1673-00x
|IP25
|4
|R10000
|195MHz
| colspan="2" |2MB
|-
|030-1673-101
|IP25
|4
|R10000
|195MHz
| colspan="2" |2MB
|-
| colspan="7" |Note: The 030-1673-101 board is unable to load IRIX 6.2, due to its use of CPU Version 3.1. 6.5.x must be used.
|}
The secondary cache of the IP19 board is installed on SIMM modules, though these are not the same ones found in the MC3's slots. These are available in capacities of 256KB and 1MB. The 1MB SIMM is not only four times larger in terms of capacity, but also has a slightly reduced latency.
{| class="wikitable"
| colspan="7" |Table of Onyx IP19 secondary cache SIMMs
|-
|SGI Part No.
|Capacity
|Latency
| colspan="4" |Color Code
|-
|030-0324-00x
|256KB
|10ns
| colspan="4" |Blue Stripe
|-
|030-0660-00x
|1MB
|8ns
| colspan="4" |Yellow Stripe
|}

==== Memory ====
Memory is installed in the Onyx using one or more MC3 boards. A deskside system can take one MC3 board, while a rack can take up to 8. Note that this means that it is impossible for an Onyx rack to have both the maximum CPU configuration and the maximum RAM configuration, as there are simply not enough EBus slots for 8 MC3s and 6 IP boards, let alone any IO4 boards. The MC3 board has 32 slots, each of which can accept a single SIMM of special ECC-protected memory. Three different models of memory SIMM exist, in capacities of 16 and 64 megabytes (with the 64MB version existing in two different variants). The following is a list of MC3 board revisions. It is believed that all revisions should be interchangeable with no effect on compatibility with other parts. However, this has not been exhaustively tested, and as such it is recommended to leave a working system's MC3 board in place when possible, as all MC3 revisions are essentially equivalent in functionality.

List of Onyx MC3 Memory Board Revisions (by SGI Part Number)030-0245-00x

* 030-0604-xxx
* 030-0607-001
* 030-0613-xxx
* 030-0614-xxx
* 030-0614-106

The following is a table of available Onyx memory SIMMs, to be installed on the MC3.
{| class="wikitable"
| colspan="7" |Table of Onyx MC3 Memory SIMMs
|-
|SGI Part No.
|Capacity
|Latency
|Color Code
| colspan="3" |Construction
|-
| colspan="7" |16MB:
|-
|030-0256-00x
|16MB
|60ns
|Pink Stripe
| colspan="3" |Single PCB
|-
| colspan="7" |64MB:
|-
|030-0257-001
|64MB
|60ns
|Purple Stripe
| colspan="3" |Dual-PCB ("Sandwich")
|-
|030-0257-002
|64MB
|60ns
|Purple Stripe
| colspan="3" |Single PCB
|}

==== Graphics ====
Throughout its lifespan, the Onyx was available with four different graphics options. Initially released with a choice of RealityEngine2 or VTX, options for Extreme graphics and InfiniteReality were introduced later.

The performance characteristics of these graphics options are provided in the table below, for easy comparison.
{| class="wikitable"
| colspan="7" |Performance Characteristics and Features of Onyx Graphics Options
|-
|
|RealityEngine2
|VTX
|InfiniteReality
| colspan="3" |Extreme
|-
|Anti-aliased vectors/sec
|2.0M
|1.0M
|7.4M
| colspan="3" |?
|-
|Triangle Meshes/sec
|1.6M
|1.1M
|11M
| colspan="3" |?
|-
|T-Mesh Gouraud Z, lit
|1.0M
|813K
|?
| colspan="3" |?
|-
|T-Mesh Textured
|988K
|600K
|?
| colspan="3" |?
|-
|Quad Strips, Gouraud, Z
|988K
|600K
|?
| colspan="3" |?
|-
|Pixel Fill, smooth, Z
|90M (1x RM )
180M (2x RM)
360M (4x RM)
|90M
|224M (1x RM)
~450M (2x RM)
"&gt;800M" (4x RM)
| colspan="3" |?
|-
|Pixel Fill, Textured, AA
|55M (1x RM)
~115M (2x RM)
230M (4x RM)
|Presumably 55M
|194M (1x RM)
~400M (2x RM)
"&gt;750M" (4x RM)
| colspan="3" |?
|-
|Trilinear Interpolations/sec
|40M (1x RM)
80M (2x RM)
160M (4x RM)
|Presumably 40M
|"&gt;200M" (1x RM)
~400M (2x RM)
"&gt;800M" (4x RM)
| colspan="3" |?
|-
|Convolutions 5x5 separable
|20M
|?
|? (SGI says "TBD")
| colspan="3" |?
|-
|Z-Buffer
|32-bit Integer
|32-bit Integer (?)
|24-bit Floating Point
| colspan="3" |?
|-
|Color
|48-bit RGBA
|48-bit RGB
|48-bit RGBA
| colspan="3" |?
|-
|Color Planes
|192
|192
|192
| colspan="3" |?
|-
|Overlay Planes*
|8
|8
|16
| colspan="3" |?
|-
|Underlay Planes*
|8
|8
|None (?)
| colspan="3" |?
|-
|Max Bits-per-pixel
|256 (1x RM)
512 (2x RM)
1024 (4x RM)
|256
|256 (1x RM)
|512(?) (2x RM)
|1024 (4x RM)
|?
|-
|Texture Memory
|4MB (RM4)
16MB (RM5)
|4MB (RM4)
16MB (RM5)
|16MB (RM6-16)
64MB (RM6-64)
| colspan="3" |?
|-
|Framebuffer Size
|40MB (1x RM)
80MB (2x RM)
160MB (4x RM)
|40MB
|80MB (1x RM)
160MB (2x RM)
320MB (4x RM)
| colspan="3" |?
|-
|Display
|VGA to non-interlaced HDTV (32-bit) or 1600x1200 (48-bit)
|VGA to 1280x1024
|VGA to non-interlaced HDTV
| colspan="3" |?
|-
|32-pixel Read (/sec? meaning unclear.)
|28.3M
|21.1M
|?
| colspan="3" |?
|-
|32-pixel Write (/sec? meaning unclear.)
|29.1M
|26.8M
|?
| colspan="3" |?
|}
Note: Overlay and underlay plane specifications are confusingly worded in sources, and should be taken with

a grain of salt. Meaning of "32-pixel" measurements is unknown, and they are provided verbatim, as listed in

the original source (sgistuff.net). Numbers for dual-RM setups may be interpolated from listed single and quad

specifications, marked with ~ when 4-RM measurement is not precisely 4x the 1-RM measurement. BPP of 512

in dual-RM IR setup interpolated from single being 256 and quad being 1024, however an SGI brochure lists

the dual-RM i-Station as 1024. This is believed to be an error. This brochure also lists some InfiniteReality details

as "greater than" a certain measurement (presumably a conservative estimate). This "&gt;SOMETHING" format is

preserved here. Details for Extreme Graphics are unknown at this time, and should be determined and added.

VTX specs marked "Presumably" are taken from an IR/RE2 comparison with no mention of VTX, and are based

on the single-RM RE2 figure (as VTX is architecturally identical, but has only one RM).

A Note on "RM"

The RealityEngine2, VTX, and InfiniteReality graphics options for the Onyx all utilize a board called the RMx, x being a version. In the case of the RealityEngine2 and VTX, this can be either the RM4 or RM5, whereas InfiniteReality uses one of two variants of the RM6 (RM6-16 or RM6-64). While, in most discussions, this board is referred to simply as the "RM", the meaning of the acronym is less clear than one might imagine. It appears that the majority of Onyx owners, as well as, in many cases, SGI themselves (see their website, circa 1994), refer to the board as the "Raster Manager". However, in the technical papers for both the RealityEngine2 and the InfiniteReality, the authors refer to it as the "Raster Memory" board. Because of this, it appears that, within SGI, there was either disagreement or confusion as to what "RM" stood for. While both would make for the "RM" acronym, it is generally accepted that "Raster Manager" makes more sense (as, while the board does contain memory, it also performs a significant amount of processing, rather than simply storing data).

RealityEngine2

RealityEngine2, often known as "RE2", was, at the time of its release, the highest end graphics option for the Onyx. While it was later repurposed as a lower-end counterpart to the new InfiniteReality, it was originally the most powerful option available. The RealityEngine2 is an improved version of the RealityEngine graphics offered in Crimson and PowerSeries systems, the differentiating factor being the replacement of the eight processor GE8 with the twelve processor GE10. Additionally, the need to terminate Raster Manager boards using a special "terminated" RM4T board (an RM4 with resistors installed in a socket on the board) was removed, with termination now being handled by the system's backplane. The RealityEngine2 consists of three types of board, installed in specialized graphics slots on the backplane.
{| class="wikitable"
| colspan="7" |Table of RealityEngine2 Boards
|-
|SGI Part No.
|Board Name
|Connected to Edge Connector?
|Function
| colspan="3" |Notes
|-
|030-0325-00x
|GE10
|No
|Geometry Engine - Perform geometric graphics calculations
| colspan="3" |N/A
|-
|030-0513-00x
|DG2
|Yes
|Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0359-001 RM4
|Yes
|Raster Manager - Generate image data from geometry
| colspan="4" |40MB framebuffer RAM per RM4, 4MB texture RAM regardless of board count.
|-
|030-0360-001
|RM4T
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |Like RM4, but terminated for pre-Onyx systems. Resistors in jumper block must be removed if installed in Onyx.
|-
|030-0347-00x
|RM5
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |40MB framebuffer RAM per RM5, 16MB texture RAM regardless of board count.
|-
|030-0506-00x
|PAB1
|No
|Paddleboard Interface - Connect RealityEngine2 to Sirius Video board
| colspan="3" |Connects to DG2. Not needed if Sirius Video is not installed.
|}
The GE10 board contains 12 Geometry Engines, at the center of each is an Intel I860XP (not to be confused with the similar but mostly unrelated terms "i386", "x86", "i586", and so-on) RISC processor. While the i860 family of processors never saw use as widespread as hoped, they were found in numerous other niche uses at the time, such as the NeXTcube's NeXTdimension color graphics board, as well as computers from Oki, Stardent, Hauppauge, and Olivetti. It also saw use in Intel's iPSC/860 and Paragon series supercomputers. In the RealityEngine2, these i860XP processors are used to perform geometry calculations for graphics. Each one of these chips has a combined ALU plus floating point performance of 100 megaflops, meaning that, multiplied by the Geometry Engines on the board, each containing one processor, the total compute performance of the GE10 board is 1.2 gigaflops. Each i860XP processor is provided with two megabytes of DRAM. The GE10 also houses the command processor, which is used to control the graphics subsystem and to implement the OpenGL graphics language. The output of these twelve individual geometry engines is transmitted on the Triangle Bus, for use by the RM board. Interestingly, the design of the Triangle Bus on the RealityEngine2's GE10 board is identical to that of said Triangle Bus on the original RealityEngine's GE8 board. While the increased load of the GE10's four extra geometry engines does increase utilization of Triangle Bus bandwidth, the bus was designed to support more than twice the bandwidth required by the original RealityEngine, meaning that in theory, it would work even with 16 Geometry Engines. This meant that the Triangle Bus did not need to upgraded or redesigned during the development of the GE10. The GE10 board does not connect to the edge connector board, and as such installation of a GE10 only requires that the board be inserted into the backplane, like a regular EBus or VME board.

The RM board inputs geometry data from the Triangle Bus, and outputs digital video data to the DG2. The RM board consists of two main types of processor, the Fragment Generator and the Image Engine. Each Raster Manager board consists of five Fragment Generators, with each Fragment Generator driving sixteen Image Engines. While the functionality of the Raster Manager is complex and spans many different tasks (as discussed in the "RealityEngine Graphics" paper, linked below), the basic architecture of the board inputs data from the GE10's triangle bus, before distributing it between five Fragment Generators. The Fragment Generator consists of four ASICs and eight 16 megabit (2 megabyte) DRAM chips, for a total of 16 megabytes per Fragment Generator and 80 megabytes per RM board. The output of the Fragment Generator is then fed into the input of the Image Engine. The RM4 board contains 20 IMP7 Image Engine chips, each of which contains four individual Image Engines. Each one of these IMP7 chips is surrounded by four four megabit (512 kilobyte) DRAM chips, one for each Image Engine inside. The output of these 80 Image Engines is then output to the DG2 board, by way of the edge connector board, which must be installed. The RM4 board provides 40MB of framebuffer memory per board, and adding more RM4 boards can increase this to a total of 160MB (in a four board setup). The RM4 also provides 4MB of texture RAM, though this capacity is not increased by the addition of further RM4 boards. The closely related RM4T is simply an RM4 with some resistors installed in a jumper block towards the rear of the board, for use as a terminated RM4 in a Crimson or PowerSeries system. If installing an RM4T board in an Onyx, these resistors should be removed from the jumper block prior to use, as the Onyx does not require Raster Manager termination. The newer RM5 maintains the same 40MB of framebuffer RAM, but increases texture RAM to 16MB, again not increased when additional boards are installed.

The DG and RM boards must be connected using an edge connector board, installed at the front of the cardcage and connecting all boards below it. The part number of this edge connector is 030-0233-001. This board carries 160 serial, one-bit 50mhz data paths, which together carry the output of the Image Engines to the DG2. In a single-RM system, half of these paths are used, one for each of the 80 Image Engines. In a dual-RM setup, each data path is assigned to a single Image Engine, with all 160 used. In a quad-RM system, these data paths are multiplexed, with each path carrying the output of two Image Engines. This multiplexing is likely the primary reason why a triple-RM system is not possible, as it would require a strange configuration, such as a half-multiplexed, half-direct use of all 160 paths, or some other special-case implementation. With all 160 paths in use, this board provides a bandwidth of 500 megabytes per second.

On the receiving end of the output of the Image Engines is the DG2 board. This board generates the video outputs exposed on the graphics bulkhead's connectors. The data from the Image Engines is first reassembled into what is effectively a digital video signal by ten crossbar ASICs on the DG2, before the image is dithered from 12- to 8-bit color and passed through Digital-to-Analog converters (DACs) for output to the monitor. Like the RM boards, the DG2 board must be connected to the edge connector board. The DG2 board has connectors for the Graphics Bulkhead, which is installed lower in the chassis and connects to it via ribbon cables.

VTX

VTX is a cost-reduced variant of the flagship RealityEngine2 graphics. Architecturally, a VTX subsystem is identical to a RealityEngine2, however it contains half the Geometry Engines and is limited to a single Raster Manager board. While the single RM board and the DG board are identical to those used in a RealityEngine2, VTX replaces the twelve-GE GE10 board with the six-GE GE10V. An SGI Periodic Table from 1993 lists many variants of Onyx in otherwise-identical VTX and RealityEngine2 configurations. This conveniently allows the reader to determine the price of a VTX subsystem relative to a RealityEngine2, as in all cases, systems with VTX graphics cost $40,000 USD less than their RealityEngine2 counterparts. Despite this significant cost saving to the original buyer, it appears that today, at least with regards to systems owned by collectors and those sold on the used market, VTX-powered Onyxes are significantly less common than RealityEngine2 models, perhaps indicating that the lower cost of VTX was not worth the reduced performance to many original buyers. It appears that SGI may have responded to this apparent lack of sales later in the Onyx's life cycle, with late-era Onyx marketing materials usually omitting the option of VTX entirely (though this could also be said to be because of the introduction of the new InfiniteReality graphics subsystem, effectively rendering the once high-end RealityEngine2 the Onyx's budget graphics offering).

InfiniteReality

InfiniteReality is the later of the two flagship graphics options offered for the Onyx. Being the successor to the RealityEngine2, InfiniteReality is the most powerful graphics option available for the Onyx. Like the RealityEngine2 subsystem before it, InfiniteReality consists of three types of board, the GE, DG, and RM. The primary goal of InfiniteReality was to deliver graphics of a quality similar to that of RealityEngine2 at an increased frame rate. A key goal during the development of InfiniteReality's architecture was that it would not only be fully compatible with the Onyx (in addition to the later, higher-bandwidth Onyx2), but that it would be able to utilize most of its performance on both systems. This affected many elements of the boardset's design, from its physical partitioning into GE, RM, and DG boards (so as to fit into the graphics slots in an Onyx), to its use of a display list subsystem with significant architectural changes to that used in the RealityEngine2 (see linked InfiniteReality: A Real-Time Graphics System paper). These architectural changes were necessary to adequately utilize the InfiniteReality in the Onyx, which interfaced with its graphics at a data rate of approximately 200MB/s, in addition to the roughly twice-as-fast Onyx2, which managed 400MB/s.

Like the RealityEngine2, the InfiniteReality uses one GE board, one DG board, and one, two, or four RM boards, connected to the DG via frontplane card-edge connector board. It should be noted that InfiniteReality's RM boards have a greater power consumption than those used in the RealityEngine2, and, as such, only one or two can officially be used in a deskside (while four is limited to a rack). Despite this limitation, it is rumored that, by installing the power boards from a rack system in a deskside, the system could theoretically power four RMs. While it may be possible to provide sufficient power for the additional boards in a deskside, cooling them is still likely to be difficult for the deskside's smaller fans. While a four-RM deskside would certainly be a rare (possibly even unique), powerful, and compact system, those attempting this configuration should exercise extreme caution, understand that they risk severely damaging their system (especially if it seriously overheats), and should understand that this configuration is unsupported and potentially not even possible. Those seeking a reliable, known-good 4-RM InfiniteReality system are advised to look into an Onyx or Onyx2 rack system, where four RMs is an official configuration, and the system already has the necessary cooling and power capacity without any modification.
{| class="wikitable"
| colspan="7" |Table of InfiniteReality Boards
|-
|SGI Part No.
|Board Name
|Connected to Edge Connector?
|Function
| colspan="3" |Notes
|-
|030-0681-003
|GE12-4
|No
|Geometry Engine - Perform geometric graphics calculations
| colspan="3" |"-4" meaningless on Onyx, denotes 4 GEs. Onyx2's GE14 also had a 2 GE "-2" version (in Reality Graphics systems).
|-
|030-0686-004
|DG4-2
|Yes
|Two-channel Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0687-004
|DG4-8
|Yes
|Eight-channel Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0683-004
|RM6-16
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |80MB framebuffer RAM per RM6-16, 16MB texture RAM regardless of board count.
|-
|030-0684-004
|RM6-64
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |80MB framebuffer RAM per RM6-64, 64MB texture RAM regardless of board count.
|-
|030-0506-00x
|PAB2
|No
|Paddleboard Interface - Connect InfiniteReality to Sirius Video board
| colspan="3" |Connects to DG4-2 or DG4-8. Not needed if Sirius Video is not installed.
|}
Like in the RealityEngine2, data moving through the InfiniteReality begins on the GE board. It is accessed from the host system using the Host Interface Processor, which then provides it to the Geometry Distributor. The Geometry Distributor handles distribution of geometry processing workload among the GE board's four Geometry Engines. The Geometry Distributor is capable of distributing data using either a round-robin or least-busy distribution scheme, though least-busy has a slight performance advantage. The Geometry Distributor provides data to the Geometry Engines in the form of commands, each of which contains an identifier assigned by the Geometry Distributor. The Geometry-Raster FIFO buffer later uses these identifiers to reconstruct the order of the commands before they were sent to the Geometry Engines.

Unlike RealityEngine2's twelve Intel i860 XP processors, InfiniteReality uses four custom in-house ASICs. The Geometry Engine chips used by InfiniteReality each contain three cores, meaning that, like it's predecessor's 12 i860 XPs, the InfiniteReality could be said to have twelve processors for geometry (three in each of the four ASICs). However, this analogy should be used with caution. While the RealityEngine2 truly did have 12 Geometry Engines, each three-core InfinteReality ASIC contains only one 2560-word (32-bit words) on-chip memory, shared by all three of its cores. As such, even ignoring the fact that they are no longer on separate chips, the cores that make up an InfiniteReality Geometry Engine are not as independent with regards to memory as the Geometry Engines are on the RealityEngine2 (where each i860 XP has access to 2MB of its own, off-chip DRAM). This single memory for all three cores also allows them to easily share data, if necessary.

At the output of the four Geometry Engines lies the Geometry-Raster FIFO, an SDRAM-based FIFO buffer capable of storing up to 65536 vertices. As stated above, this FIFO is also responsible for properly ordering its data, based on the identifiers assigned by Geometry Distributor.

The data then moves from the GE board to the RM boards, via the Vertex Bus. While the purpose of the Vertex Bus (to carry data between the GE and RM boards) is similar to that of the RealityEngine2's Triangle Bus, it is implemented differently (see paper linked below), resulting in a significant performance improvement. Data sent over the Vertex Bus is broadcast to all Fragment Generators. The InfiniteReality RM board contains a single Fragment Generator and 80 Image Engines. The Fragment Generator is, as was also the case with its predecessor, composed of multiple chips (the SC Scan Converter, TA Texel Address Calculator, eight TM Texture Memory controllers, and four TF Texture Filtering ASICs). Like on the RealityEngine2, data from the GE board is first processed by the Fragment Generator, then by the Image Engines. Because there is only one per RM board, an InfiniteReality RM board's single Fragment Generator uses all 80 of the image engines on the board, unlike on the RealityEngine2, where each of the five Fragment Generators is given 16 of the 80 total Image Engines. The InfiniteReality also continues the trend of combining four individual Image Engines onto a single Image Engine chip, meaning that only 20 Image Engine chips are needed.

Two variants of the Onyx InfiniteReality RM board are available. The RM6-16 has 16MB of Texture RAM (TRAM), while the RM6-64 has 64MB. Each RM board maintains one copy of texture RAM, meaning that, while the amount of physical texture memory in a system increases when additional RM boards are installed, the amount of usable texture memory remains the same, as the memory on the newly-installed RM board(s) is used simply duplicate the data on the existing RM(s). Because each board must retain its own copy of texture RAM, RM6-16 and RM6-64 boards cannot be mixed in a single system (as, having only a quarter the texture memory, an RM6-16 would be unable to store a full copy of the texture memory contents of an RM6-64). Both the RM6-16 and RM6-64 have 80MB of framebuffer RAM per RM board, double the 40MB seen on the RealityEngine2. Unlike TRAM, framebuffer RAM is not duplicated between RM boards, meaning that more RM boards will increase the total amount of framebuffer RAM in the graphics subsystem, up to a maximum of 320MB (with four RM boards).

Like on the RealityEngine2, the output of the RM boards is sent to the DG board via an edge connector board mounted at the front of the cardcage. The edge connector spans the four RMs, connecting to each, and also connects to the DG board, but does not connect to the GE board or any other boards in the cardcage. This edge connector carries 160 serial data paths, the same configuration used in the RealityEngine2, however their use is more flexible on InfiniteReality systems. The RealityEngine2 utilizes one path per Image Engine in one-RM and two-RM configurations, and multiplexes the outputs of each pair of Image Engines onto a single path in a four-RM configuration. This means that, while the video bandwidth of the frontplane is fully utilized in two-RM and four-RM setups, where all 160 paths are driven by at least one Image Engine, single-RM systems utilize only half of the bandwidth, leaving the other 80 paths unused. Though an InfinteReality system also has only 160 paths for its potential 320 Image Engines, it uses them more efficiently in single-RM configurations. While two RMs will assign one path to each of the 160 Image Engines, and four RMs will multiplex the output of 320 Image Engines onto 160 paths, single-RM InfiniteReality systems allow each of the 80 Image Engines to drive two of the 160 data paths on the frontplane, doubling per-Image-Engine bandwidth. Since InfiniteReality systems use all 160 data paths in all configurations, the bandwidth of the InfiniteReality frontplane is a fixed 1200MB/s.

These 160 signals are recieved by four ASICs at the input of the Display Generator board (these ASICs also add the cursor on top of the incoming video). The video is then sent to one of the Display Generator's two or eight (see below) channels. A DG channel is able to resize its video in realtime (e.g. for output as NTSC/PAL video), and can also control the timing of its output. This timing control is the purpose of the Genlock and Swap Ready BNC connectors on the graphics bulkhead, and is discussed in greater depth in the "InfiniteReality: A Real-Time Graphics System" paper linked below. The channel's 12-bit-per-component digital video signal is then passed through 8-bit DACs, which generate the final analog video signal. It should be noted that Channel 1 contains additional hardware, not found on other channels, allowing it to also output composite and S-Video signals.

InfiniteReality's DG4 board is available in two variants. The DG4-2 has two channels, and was the lower-end "standard" option, while the higher-end DG4-8 has eight channels. It should be noted that the DG4-2 PCB has footprints for the components required to provide extra six channels, however, these components are unpopulated. Particularly noticeable are the footprints for the six large BGA chips along the edge of the board, as well as the six QFPs beside them. Towards the middle of the board is a connector for the PAB2 Sirius Video paddleboard, which must be installed if the InfiniteReality boardset is being used alongside a Sirius Video board. The DG4 board has connectors for the Graphics Bulkhead, which is installed lower in the chassis and connects to it via ribbon cables.

Extreme Graphics

Extreme Graphics is the lowest-end graphics option available for the Onyx. It was also available in the Indigo2, where it was the highest-end option until the introduction of IMPACT graphics in 1995. While Extreme Graphics boardsets are relatively common in Indigo2s, they are a rare and largely undocumented option in the Onyx. While it is generally understood that the graphics boardset itself is identical to the one found in an Indigo2, the hardware used to connect it to the Onyx (which does not normally have GIO64 slots) is poorly documented. Further information about the adapters required for this configuration can be found in the "Architecture" section above. The graphics hardware itself is simply a regular Extreme Graphics boardset (see Indigo2). This configuration is rare, and this, combined with the fact that it is rarely mentioned in official SGI documents, is likely the reason for the scarcity of information surrounding it.

==== I/O ====
The IO4 I/O Controller implements the basic I/O functions for Onyx systems:

* Ethernet Controller
* two fast/wide 16 bit SCSI-2 controllers
* four serial ports (3x RS232, 1x RS422)
* a parallel port
* two Flat Cable Interfaces (for VME or Graphics)

In Onyx Deskside systems 1 IO4 controller can be installed, in rackmount Onyxes up to 6 of these boards can be installed.

=== Operating System Support ===
It is recommended to run IRIX 6.5.22 on all revisions/versions of this machine.

=== Troubleshooting ===
No power-on

If a previously working Onyx with no known power supply issues suddenly refuses to power on (specifically no DC GOOD light, no front panel controller functioning) it is possible the Dallas chip located on the System Controller Board (rear access panel of the Onyx) has gone bad. Replacing the Dallas DS12887 with a new production version will allow the system to power on correctly.

=== Links ===

* "RealityEngine Graphics" paper: &lt;nowiki&gt;http://www.sgistuff.net/hardware/graphics/documents/K.Akeley-RealityEngine.pdf&lt;/nowiki&gt;
* "InfiniteReality: A Real-Time Graphics System" paper: &lt;nowiki&gt;http://people.csail.mit.edu/ericchan/bib/pdf/p293-montrym.pdf&lt;/nowiki&gt;</text>
    <sha1>a2e9212290b2f58f6066f87c4b561f6b2c5eca8f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Tezro-frontal.jpg</title>
  <ns>6</ns>
  <id>54</id>
  <revision>
    <id>62</id>
    <timestamp>2025-02-07T04:09:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="29" xml:space="preserve">Front profile of an SGI Tezro</text>
    <sha1>f5b14552e0142306a23c8ce2dcebd3dea2ddeead</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Tezro</title>
  <ns>0</ns>
  <id>55</id>
  <revision>
    <id>63</id>
    <timestamp>2025-02-07T04:09:54Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3439" xml:space="preserve">For the rackmount variant of the SGI Onyx 350 branded as a Tezro, see [[Origin 350]].
[[File:Tezro-frontal.jpg|thumb|SGI Tezro, Front-profile view]]


The Silicon Graphics Tezro (styled as silicon graphics tezro) is a high-end workstation introduced by Silicon Graphics in July 2003 to replace the Octane 2. Built on the Chimera architecture, the Tezro is closely related to the Origin 350 and Onyx 350 systems offered by SGI during the same time period and shares the graphics module, node boards, drive sleds and some cooling parts. The Tezro is essentially a single-node Onyx 350 mounted on its side and connected like a sandwich to the IO backplane. The system was succeeded late in 2006 to early 2007 with the launch of the Prism. The Onyx4 launched alongside it, though that utilized the ATi developed UltimateVision. This distinction makes the Tezro the last machine designed by SGI to use an in-house graphics architecture. The Tezro is highly sought after in the collector market for its style, power, and for the distinction of being SGI's last MIPS workstation.

=== Features ===
The Tezro is powered by the MIPS R16000 series of processors and came in dual and quad CPU node boards. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|4MB
|700,800
|700,800
|-
|8MB
|700,800
|700,800
|-
|16MB
|1000MHz
|1000MHz
|}
The Tezro can take anywhere from 512M to 8G of DDR RAM, using the same proprietary DIMMs as the Fuel, Origin/Onyx 300,350, and 3000 series.

A maximum of two 300GB U160 SCSI drives can be added to the system via the front access panel using the Origin/Onyx 350-style sleds.

Tezro supports the V10 and V12 graphics options. Dual-channel options were produced, allowing up to two 1920x1200 displays. The V12 was the only **shipped** configuration, but some machines were field replaced with V10s, or have been replaced by end users to re-purpose V12s for other machines.

The IO9 card provides SCSI backplane support, 3.5mm Audio, and a 100Mbit Ethernet port. Six PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more. A DMedia card can be added to provide DMedia support as well.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== Hardware Problems ===
The fans are controlled by environmental monitoring and the system will refuse to boot if the fans do not all respond.

The 1GHz/1000MHz CPU boards are known to overheat quickly due to inadequate airflow in the case. It's advisable to set external temperature monitoring and alarms and to not run the machine unattended, as this risks VRM or CPU failure. The latter means a new node board.

=== Form Factor and Transportation ===
The Tezro measures 21 x 14 x 17 inches in L x W x H dimensions and weighs at minimum 61lbs, more if it is heavily equipped. The front access panel is very fragile, and the system should not be held by the plastics as they grow brittle with age.

The unit has wheels on the rear, allowing for easy movement on hard surfaces. It should be carried gently and preferably with the rear of the unit supporting the weight, not the sides or the front.

=== Operating System Support ===
The Tezro was supported beginning with IRIX 6.5.15, through the final 6.5.30 release.</text>
    <sha1>bb54e913d2aed3b20310e0307fe085e6f575f76f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Origin 2000 Deskside .jpg</title>
  <ns>6</ns>
  <id>56</id>
  <revision>
    <id>64</id>
    <timestamp>2025-02-07T04:12:15Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="30" xml:space="preserve">An Origin 2000 Deskside system</text>
    <sha1>b81db036e7f995b7f1f4a06b0725bbc48af556cb</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Deskside Oriigin 2000 Profile.jpg</title>
  <ns>6</ns>
  <id>57</id>
  <revision>
    <id>65</id>
    <timestamp>2025-02-07T04:13:38Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="31" xml:space="preserve">Origin 2000 Deskside in profile</text>
    <sha1>6e4aa15b6e41871ee94014c8591ae2b2a0814f74</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Origin 2000</title>
  <ns>0</ns>
  <id>58</id>
  <revision>
    <id>66</id>
    <timestamp>2025-02-07T04:16:05Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3261" xml:space="preserve">For the graphics deskside variant, see the [[Onyx2]] article
[[File:Origin 2000 Deskside .jpg|thumb|Front view of an Origin 2000 Deskside]]
The SGI Origin 2000, code name ''Lego'', is the successor of the SGI Challenge line. Sold in deskside, rack and multi-rack configurations, the Origin 2000 is a highly modular and scalable system.
[[File:Deskside Oriigin 2000 Profile.jpg|left|thumb|Another view of an Origin 2000 Deskside in profile]]

=== Features ===
Each Origin 2000 module is based on nodes that are plugged into a midplane. Each module can contain up to four node boards, two router boards and twelve XIO options. The modules are then mounted inside a deskside enclosure or a rack. Deskside enclosures can only contain one module, while racks can contain two. In configurations with more than two modules, multiple racks are used.

The following table shows a list of models and their possible configurations:
{| class="wikitable"
|Model
|CPUs
|Memory
|I/O
|Chassis
|-
|Origin 2100
|2 to 8
|Up to 16 GB
|12 XIO
|Deskside
|-
|Origin 2200
|2 to 8
|Up to 16 GB
|12 XIO
|Deskside
|-
|Origin 2400
|8 to 32
|Up to 64 GB
|96 XIO
|1-4 Racks
|-
|Origin 2800
|32 to 128
|Up to 256 GB (512 GB unsupported)
|384 XIO
|1 to 9 racks (with Meta Router)
|}
A 3-slot PCI cage can be installed as well as a maximum of 10 XIO cards, giving a massive amount of expandability. This is in addition to 5 hard disks and one 5.25 option drive.

==== CPU ====
The following table shows the possible CPU configurations.
{| class="wikitable"
|Processor
|Clockspeed
| colspan="3" |Cache
|-
|R10000
|180 MHz
|1MB
| colspan="2" |R10000
|-
|R10000
|195 MHz
|4MB
| colspan="2" |R10000
|-
|R10000
|250 MHz
|4MB
| colspan="2" |R10000
|-
|R12000
|300 MHz
|8MB
| colspan="2" |R12000
|-
|R12000
|350 MHz
|4MB
| colspan="2" |R12000
|-
|R12000
|400 MHz
|8MB
| colspan="2" |R12000
|-
|R14000
|500 MHz
|8MB
| colspan="2" |R12000
|}

=== Memory ===
DIMMs are available in sizes of 16, 32, 64 and 256 MB. The memory modules used in the Origin 200 and Origin 2000 / Onyx 2 are of the same type. To support the Origin 2000 distributed shared memory model, the memory modules are proprietary and include directory memory, which contains information on the contents of remote caches for maintaining cache coherency, supporting up to 32 processors. Additional directory memory is required in configurations with more than 32 processors. The additional directory memory is contained on proprietary DIMMs that are inserted into eight DIMM slots set aside for its use.

==== IO6 ====
An IO6 base I/O board is present in every system. It is a XIO card that provides:

* a 10/100BASE-TX Ethernet port
* 2 Serial ports provided by dual UARTs
* 1 internal Fast 20 UltraSCSI single-ended port
* 1 external wide UltraSCSI, singled ended port
* 1 real-time interrupt output for frame sync
* 1 real-time interrupt input (edge triggered)

Also on the card is the Flash PROM, NVRAM and real time clock of the system.

==== PCI ====
The system can utilize PCI with the addition of an Origin 2000 XIO PCI "Shoebox" or individual XTalk PCI adapters inserted in the cage. These are the same sort form factor as Octane units.

=== Operating System Support ===
IRIX Versions from 6.4 to 6.5.30 supports the Origin 2000.</text>
    <sha1>5996bf41effff69208e057b22d6d3cd0b70c962c</sha1>
  </revision>
  <revision>
    <id>101</id>
    <parentid>66</parentid>
    <timestamp>2025-02-08T04:04:55Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3357" xml:space="preserve">For the graphics deskside variant, see the [[Onyx2]] article
[[File:Origin 2000 Deskside .jpg|thumb|Front view of an Origin 2000 Deskside]]
The SGI Origin 2000, code name ''Lego'', is the successor of the SGI Challenge line. Sold in deskside, rack and multi-rack configurations, the Origin 2000 is a highly modular and scalable system.
[[File:Deskside Oriigin 2000 Profile.jpg|left|thumb|Another view of an Origin 2000 Deskside in profile]]

=== Features ===
Each Origin 2000 module is based on nodes that are plugged into a midplane. Each module can contain up to four node boards, two router boards and twelve XIO options. The modules are then mounted inside a deskside enclosure or a rack. Deskside enclosures can only contain one module, while racks can contain two. In configurations with more than two modules, multiple racks are used.

The following table shows a list of models and their possible configurations:
{| class="wikitable"
|Model
|CPUs
|Memory
|I/O
|Chassis
|-
|Origin 2100
|2 to 8
|Up to 16 GB
|12 XIO
|Deskside
|-
|Origin 2200
|2 to 8
|Up to 16 GB
|12 XIO
|Deskside
|-
|Origin 2400
|8 to 32
|Up to 64 GB
|96 XIO
|1-4 Racks
|-
|Origin 2800
|32 to 128
|Up to 256 GB (512 GB unsupported)
|384 XIO
|1 to 9 racks (with Meta Router)
|}
A 3-slot PCI cage can be installed as well as a maximum of 10 XIO cards, giving a massive amount of expandability. This is in addition to 5 hard disks and one 5.25 option drive.

==== CPU ====
[[File:Onyx2 rack.jpg|thumb|An Origin 2000 rack unit is seen here with an onyx2 graphics unit]]
The following table shows the possible CPU configurations.
{| class="wikitable"
|Processor
|Clockspeed
| colspan="3" |Cache
|-
|R10000
|180 MHz
|1MB
| colspan="2" |R10000
|-
|R10000
|195 MHz
|4MB
| colspan="2" |R10000
|-
|R10000
|250 MHz
|4MB
| colspan="2" |R10000
|-
|R12000
|300 MHz
|8MB
| colspan="2" |R12000
|-
|R12000
|350 MHz
|4MB
| colspan="2" |R12000
|-
|R12000
|400 MHz
|8MB
| colspan="2" |R12000
|-
|R14000
|500 MHz
|8MB
| colspan="2" |R12000
|}

=== Memory ===
DIMMs are available in sizes of 16, 32, 64 and 256 MB. The memory modules used in the Origin 200 and Origin 2000 / Onyx 2 are of the same type. To support the Origin 2000 distributed shared memory model, the memory modules are proprietary and include directory memory, which contains information on the contents of remote caches for maintaining cache coherency, supporting up to 32 processors. Additional directory memory is required in configurations with more than 32 processors. The additional directory memory is contained on proprietary DIMMs that are inserted into eight DIMM slots set aside for its use.

==== IO6 ====
An IO6 base I/O board is present in every system. It is a XIO card that provides:

* a 10/100BASE-TX Ethernet port
* 2 Serial ports provided by dual UARTs
* 1 internal Fast 20 UltraSCSI single-ended port
* 1 external wide UltraSCSI, singled ended port
* 1 real-time interrupt output for frame sync
* 1 real-time interrupt input (edge triggered)

Also on the card is the Flash PROM, NVRAM and real time clock of the system.

==== PCI ====
The system can utilize PCI with the addition of an Origin 2000 XIO PCI "Shoebox" or individual XTalk PCI adapters inserted in the cage. These are the same sort form factor as Octane units.

=== Operating System Support ===
IRIX Versions from 6.4 to 6.5.30 supports the Origin 2000.</text>
    <sha1>7303e037326ce1aa9c8c3f90ce7b129a30765028</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Origin350 .jpg</title>
  <ns>6</ns>
  <id>59</id>
  <revision>
    <id>67</id>
    <timestamp>2025-02-07T04:19:36Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25" xml:space="preserve">An Origin 350 Rack Server</text>
    <sha1>b7f6c3f9348e35a98388f765f24abe6e2bef7a93</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Origin 350</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>68</id>
    <timestamp>2025-02-07T04:22:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Origin350 .jpg|thumb|400x400px|Origin 350 Server]] The SGI Origin 350, and its graphics-equipped sibling the '''Onyx350''', is a rack-mounted, mid range server sold by Silicon Graphics from 2003 to 2007. This system uses MIPS-based processors and offers a number of advances over the Origin 300 model that preceded it. The 350 was offered in two to 32 processor configurations, at speeds ranging from 600 to 1,000MHz over the lifetime of the model. The Origin 350 is a..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6517" xml:space="preserve">[[File:Origin350 .jpg|thumb|400x400px|Origin 350 Server]]
The SGI Origin 350, and its graphics-equipped sibling the '''Onyx350''', is a rack-mounted, mid range server sold by Silicon Graphics from 2003 to 2007. This system uses MIPS-based processors and offers a number of advances over the Origin 300 model that preceded it. The 350 was offered in two to 32 processor configurations, at speeds ranging from 600 to 1,000MHz over the lifetime of the model. The Origin 350 is a member of the Chimera family (IP53), which includes Origin 350, Onyx 350, and the Tezro Rackmount. All three systems have the same basic hardware - the Origin 350 (Chimera Server) with a VPro card becomes the Onyx 350 (ChiBlade), and the ChiBlade can be configured into a Chimera Rackmount Workstation (Tezro Rack) using the L1's make rmws 1 command. The Chimera Rackmount Workstation cannot accept remote serial numbers, and therefore cannot be connected via NUMALink.

=== Features ===
Each CPU brick has four PCI slots across two PCI busses. Each CPU brick also has a Fuel-style XIO slot, which can accept a DMediaPro DM3 card or a VPro graphics card. The first CPU brick in a system has a single PCI slot holding an IO9 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, audio I/O and a twisted pair Ethernet connection. Other kinds of bricks are available that are dedicated to disk storage or further PCI slots.

The different configurations are:

* Base Compute Module - Includes an IO9, a SCA SCSI backplane (for disks), appropriate cables for disk backplane + IDE CDROM and a daughtercard that provides PS/2 keyboard/mouse and four additional serial ports
* Expansion Compute Modules - These may or may not include the IO9+backplane, but lacks the daughtercard/keyboard/mouse/extra serial ports
* Memory and PCI Expansion (MPX) Modules - Lacks the IO9+backplane and daughtercard/keyboard/mouse/extra serial ports.
* 2UPX Module - PCI Only Expansion Module; a standard 2U Origin 350 chassis with four PCI-X and one XIO-2 slot without processor, memory or Bedrock ASIC. Because the 2UPX does not have a BedRock ASIC, it uses the external XIO port when linked to Origin 350 Compute Modules.

An Origin 350 cannot be booted by itself without the presence of an IO9 card, it requires the IO9 to start up. If a brick lacks it, one must be installed or otherwise the brick must be numalinked.

=== CPU ===
Each brick can take dual or quad CPU configurations the same as the Tezro. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|4MB
|600,700,800
|600,700,800
|-
|8MB
|700,800
|700,800
|-
|16MB
|1000MHz
|1000MHz
|}

=== Memory ===
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Fuel, and the Tezro. There are a total of eight slots, organized into four banks of two slots. This results in a memory capacity from 512 MB to 8 GB total system memory.

All DIMMS for the Origin 350 use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

=== I/O ===
The IO9 card provides SCSI backplane support, 3.5mm Audio, and a 1Gbit Ethernet port. Three PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Origin 350 leverages NUMALink heavily to link bricks together. Each unit has a NUMALink and an XIO port, used to link various subsystems together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to eight CPU "bricks" (2 rackmount units high each) with up to four CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink3 cables going to a central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Origin 350 has a front bay for two U160 SCSI drives. It uses proprietary sleds for this purpose.

The Origin/Onyx 350, Prism, Altix 350, and Altix 450/4x00 all use the same drive carriers. These are standard parts used by a number of manufacturers, notably Intel's SC5200, SRSH4, SR1300/2300, and SR1400/2400 and Sun's v60x and v65x servers.

The units carry "Assy A65278-00x" on a sticker, where the "-00x" may end in any digit though "-005" seems common. This assembly number can be useful when searching for parts in the Internet. According to SR1300/SR2300 support documents at intel.com, the Intel accessory part number for the drive carrier is FXX2DRVCARBLK, UPC code "7 35858 14621 0" and "MM #" 835853. However note that there is some indication that Intel may recycle these accessory part numbers in the FXX- form between different models.

=== Onyx 350 ===
An Onyx 350 is an Origin 350 with a V10/V12 graphics card attached to the XIO2 slot inside, or an Origin 350 attached to a G-Brick.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator called an L3 controller.

It is recommended to use 1GHz boards in the Origin 350, not a Tezro desktop, for the reason of airflow and longevity.

=== Operating System Support ===
The Origin 350 was supported beginning with IRIX 6.5.15, and is supported through IRIX 6.5.30

Comments</text>
    <sha1>19fbff5d4785417e71df632b30c9ec33e2791427</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:O300.gif</title>
  <ns>6</ns>
  <id>61</id>
  <revision>
    <id>69</id>
    <timestamp>2025-02-07T04:24:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10" xml:space="preserve">Origin 300</text>
    <sha1>3225a004c15788054bd7fb52eb82d136e42a9be7</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Origin 300</title>
  <ns>0</ns>
  <id>62</id>
  <revision>
    <id>70</id>
    <timestamp>2025-02-07T04:24:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:O300.gif|thumb|Origin 300 rack unit]] The SGI Origin 300 is a rack-mounted, mid range server sold by Silicon Graphics from 2001 to 2004. The 300 was offered in two to 32 processor configurations, at speeds ranging from 400 to 600MHz over the lifetime of the model. The Origin 300 is not a member of the later Chimera family, though it shares superficial and functional similarities with it. Its closest relative is the SGI Fuel.   === Features === Each CPU brick has t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5142" xml:space="preserve">[[File:O300.gif|thumb|Origin 300 rack unit]]
The SGI Origin 300 is a rack-mounted, mid range server sold by Silicon Graphics from 2001 to 2004. The 300 was offered in two to 32 processor configurations, at speeds ranging from 400 to 600MHz over the lifetime of the model. The Origin 300 is not a member of the later Chimera family, though it shares superficial and functional similarities with it. Its closest relative is the SGI Fuel. 

=== Features ===
Each CPU brick has two PCI slots across a PCI bus. All compute bricks are equipped with an IO8 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, and a twisted pair Ethernet connection.

=== CPU ===
Each brick can take dual or quad CPU configurations. The CPUs are attached to the main board, thus a configuration upgrade requires removal of the entire main board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|2MB
|500
|500
|-
|4MB
|600
|600
|}

=== Memory ===
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Fuel, Origin/Onyx350. and the Tezro. There are a total of eight slots, organized into two banks of two slots. This results in a memory capacity from 512 MB to 4 GB total system memory.

All DIMMS for the Origin 300 use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory, which remains unused in the Fuel. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

=== I/O ===
The IO8 card provides SCSI backplane support, and a 100Mbit Ethernet port. Two PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Origin 300 leverages NUMALink heavily to link bricks together. Each unit has a NUMALink and an XIO port, used to link various subsystems together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to eight CPU "bricks" (2 rackmount units high each) with up to four CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink3 cables going to a central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Origin 300 has a front bay for two U160 SCSI drives. It uses proprietary sleds for this purpose.

These sleds are standard off-the-shelf parts used by a number of high-volume server manufacturers, but were apparently only used by SGI on the Origin and Onyx 300 models.

Often Origin 300 systems will be split up and the individual bricks sold to different buyers. While many of these bricks never had hard drives installed, SGI did install sleds with baffles to maintain airflow. This is good news for buyers, as the plastic baffles can be removed and hard drives installed in their place.

The units typically have a sticker on the front of the sled showing the identifier "Assy A06447-00x" where the "-00x" may end in any digit. The second line of the label includes what may be an additional part number ("203368", as seen in the thumbnail image to the right) and a manufacturing code of some kind. It is unclear whether the manufacturing code indicates time of production, plant, batch run, or something else entirely.

However the assembly number from SGI units has not always been useful when searching for replacement parts in the Internet. It was suggested that Intel part number 746797-001 may be the same OEM part.

The 746797-001 part number is referenced in some sources as being used on Intel's SR1200/2200 and ISP2150G servers (black bezel). However images from some eBay auctions appear more similar to the Origin 350-style drive sled, and indeed the Intel product guide for the SR1200 has diagrams showing a unit more similar to that used in the Origin 350.

=== Onyx 300 ===
An Onyx 300 is an Origin 300 NUMALinked to a G-Brick.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator.

=== Operating System Support ===
The Origin 300 was supported beginning with IRIX 6.5.14, and is supported through IRIX 6.5.30</text>
    <sha1>e2ac12ea5c3159815cf0ced48cb8ace3c34a62ff</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:SGI Altix 350.jpg</title>
  <ns>6</ns>
  <id>63</id>
  <revision>
    <id>71</id>
    <timestamp>2025-02-07T16:34:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">An early Altix 350</text>
    <sha1>2921464ba2efc38f4c9222fc929a0d82f065b936</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Altix 350</title>
  <ns>0</ns>
  <id>64</id>
  <revision>
    <id>72</id>
    <timestamp>2025-02-07T18:31:43Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The SGI Altix 350, is a rack-mounted, mid range server sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and while visually similar to the Origin 350, and sharing some ancillary parts, it is a clean break in design and runs RHEL and SLES Linux. The Altix 350 implements the IP57 processor, but follows the IP41 architecture from the earlier Altix 3000 systems. A system can include from 1 to 32 processors in up to 16 modules or bricks,..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4749" xml:space="preserve">The SGI Altix 350, is a rack-mounted, mid range server sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and while visually similar to the Origin 350, and sharing some ancillary parts, it is a clean break in design and runs RHEL and SLES Linux. The Altix 350 implements the IP57 processor, but follows the IP41 architecture from the earlier Altix 3000 systems. A system can include from 1 to 32 processors in up to 16 modules or bricks, with one or two NUMAlink routers connecting them. Configurations up to 8 modules can be organized in a ring topology without a router.
[[File:SGI Altix 350.jpg|thumb|Early Altix 350]]

=== Features ===
Each base module has four PCI slots across two PCI buses. The first CPU brick in a system has a single PCI slot holding an IO9 or IO10 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, audio I/O and a twisted pair Ethernet connection. The more rare IO10 is a SATA card.

The different configurations are:

* Base Module
* CMPX Expansion Module ("Cpu Memory Pci/pci-X")
* CPU Expansion Module
* NUMAlink 4 Router Module (often labeled "NL4R")

An Altix350 cannot be booted by itself without the presence of a BaseIO card. If a brick lacks it, one must be installed or otherwise the brick must be numalinked.

=== CPU ===
Each brick can take single or dual CPU configurations the same as the Prism. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="2" |CPU Configurations
|-
|CPU Cache
|Speeds (GHz)
|-
|1.5MB
|1.0, 1.4
|-
|3MB
|1.3, 1.4, 1.6
|-
|4MB
|1.4, 1.5
|-
|6MB
|1.5, 1.6
|-
|9MB
|1.6
|}

=== Memory ===
Like other first-generation Altix systems, the Altix 350 uses registered DDR DIMMs with ECC, rated at 266MHz or faster, which are commonly referred to as PC2100, PC2700, etc. Memory is organized in three banks of four DIMMs each, or twelve slots total, providing up to 24GB of RAM total per base module. DIMMs of 512MB, 1GB, and 2GB are officially supported; it is unclear as of this writing if 4GB parts will work.

=== I/O ===
The IO9 controller supports Ultra160 SCSI devices and includes an externally-accessible VHDCI port, while the IO10 controller supports SATA devices and includes a high density serial connector. Both controllers include a separate IDE interface to support optical drives.

Either IO controller provides one 1000baseT Ethernet interface. Three PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more. The BaseIO card must be installed in the bottom slot.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Altix 350 leverages NUMALink heavily to link bricks together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to sixteen CPU "bricks" (2 rackmount units high each) with up to two CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink4 cables going to one or two central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Altix 350 has a front bay for two 3.5" drives. It uses proprietary sleds for this purpose.

The Origin/Onyx 350, Prism, Altix 350, and Altix 450/4x00 all use the same drive carriers. These are standard parts used by a number of manufacturers, notably Intel's SC5200, SRSH4, SR1300/2300, and SR1400/2400 and Sun's v60x and v65x servers.

The units carry "Assy A65278-00x" on a sticker, where the "-00x" may end in any digit though "-005" seems common. This assembly number can be useful when searching for parts in the Internet. According to SR1300/SR2300 support documents at intel.com, the Intel accessory part number for the drive carrier is FXX2DRVCARBLK, UPC code "7 35858 14621 0" and "MM #" 835853. However note that there is some indication that Intel may recycle these accessory part numbers in the FXX- form between different models.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator called an L3 controller.

=== Operating System Support ===
The system can run Microsoft Windows up to Server 2008 R2 (Itanium Edition) and GNU/Linux RHEL and SLES up to versions 5 and 9 respectively.</text>
    <sha1>2863f04352d6328437d5b55f018943f29676258d</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:HP i2000.jpg</title>
  <ns>6</ns>
  <id>65</id>
  <revision>
    <id>73</id>
    <timestamp>2025-02-07T18:33:32Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">HP i2000 desktop</text>
    <sha1>08509c080514ede2bbdf64f36993e372df5a34c2</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>SGI 750</title>
  <ns>0</ns>
  <id>66</id>
  <revision>
    <id>74</id>
    <timestamp>2025-02-07T18:33:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:HP i2000.jpg|thumb|An HP i2000, the same computer branded by HP]] The Silicon Graphics 750, released in May of 2001, was the first Silicon Graphics product offered with an Itanium processor. It was intended as a development platform for developers of IRIX on MIPS applications to port their software to Linux on Itanium ahead of the release of SGI's full Itanium product line. However, after poor sales and the limited performance of the first-generation Itanium proce..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1724" xml:space="preserve">[[File:HP i2000.jpg|thumb|An HP i2000, the same computer branded by HP]]
The Silicon Graphics 750, released in May of 2001, was the first Silicon Graphics product offered with an Itanium processor. It was intended as a development platform for developers of IRIX on MIPS applications to port their software to Linux on Itanium ahead of the release of SGI's full Itanium product line. However, after poor sales and the limited performance of the first-generation Itanium processors it used became apparent, it was discontinued early, leaving SGI without an Itanium product between December 2001 and January 2003 (when the first Altix systems were introduced). A rebrand of an Intel-made Itanium developer system, it was sold by multiple manufacturers as the following products:

* Silicon Graphics 750
* Dell Precision Workstation 730
* Fujitsu-Siemens Celsius 880
* HP i2000
* IBM IntelliStation Z Pro 6894

As such, this article also applies to any of these non-SGI-sold systems. The SGI branding on the SGI 750 consists of simple stickers on the case plastic and minor software branding tweaks.

=== Specifications ===
The SGI 750 featured one or two first-generation Intel Itanium ''Merced'' processors on its processor board, up to 4GB of PC100 SDRAM on two removable Memory Expansion Cards (MECs), seven PCI expansion slots, and an AGP 4x graphics card slot fitted with an ATI XPERT 2000 PRO graphics card. It appears to have used EFI as its firmware, and included a graphical configuration tool. It was intended to be used with Linux.

=== Sources ===
&lt;nowiki&gt;http://techpubs.jurassic.nl/library/manuals/4000/007-4291-001/pdf/007-4291-001.pdf&lt;/nowiki&gt;

&lt;nowiki&gt;https://www.flickr.com/photos/tbonico/3759976892&lt;/nowiki&gt;</text>
    <sha1>143f213ee12a300a13998e07894440b049a28e81</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:An Octane2 setup.jpg</title>
  <ns>6</ns>
  <id>67</id>
  <revision>
    <id>75</id>
    <timestamp>2025-02-07T18:36:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">Octane 2 set up with monitor</text>
    <sha1>7f5810ee327b2efaa9da2d5dd4b701b63704db9f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Octane-new-logo.jpg</title>
  <ns>6</ns>
  <id>68</id>
  <revision>
    <id>76</id>
    <timestamp>2025-02-07T18:37:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42" xml:space="preserve">A late model Octane with the new SGI logo.</text>
    <sha1>fc19ed56e182367556d3f920c9764c24536570fa</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Octane2.jpg</title>
  <ns>6</ns>
  <id>69</id>
  <revision>
    <id>77</id>
    <timestamp>2025-02-07T18:38:36Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="26" xml:space="preserve">Another view of an Octane2</text>
    <sha1>fe3723d2d35cd0bec6e1443e2503479a1cb234f4</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Octane</title>
  <ns>0</ns>
  <id>70</id>
  <revision>
    <id>78</id>
    <timestamp>2025-02-07T18:38:55Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:An Octane2 setup.jpg|thumb|An Octane2 setup]] The Octane and its later version, the '''Octane2''', code named Speed Racer, is a high end workstation marketed by Silicon Graphics between 1996 and 2004. It is an SMP-capable (dual CPU) machine running the MIPS R10000 to R14000 series of processors. The main differences between the Octane2 and the Octane are configuration-related. The Octane 2 has upgraded motherboard, power supply, front plane and graphics options, b..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9227" xml:space="preserve">[[File:An Octane2 setup.jpg|thumb|An Octane2 setup]]
The Octane and its later version, the '''Octane2''', code named Speed Racer, is a high end workstation marketed by Silicon Graphics between 1996 and 2004. It is an SMP-capable (dual CPU) machine running the MIPS R10000 to R14000 series of processors. The main differences between the Octane2 and the Octane are configuration-related. The Octane 2 has upgraded motherboard, power supply, front plane and graphics options, but it's entirely possible to retrofit these upgrades to a regular Octane, creating the "Octane 1.5" as many have popularly dubbed it. 

=== Features ===
[[File:Octane-new-logo.jpg|left|thumb|An Octane late model with the "sgi" logo]]
The Octane's system-board is designated as IP30. The system is based on SGI's Xtalk (Pronounced Cross-talk) architecture. This means it does not use a system bus; instead it has a router XBOW (Pronounced cross-bow) that connects any two of its ports. One of the ports is used for the processor and memory subsystem, one is available for PCI (actually PCI-64) expansion and four are XIO slots (packet-based high-bandwidth bus, somewhat similar to HyperTransport). This makes it very similar to a single node of the SGI Origin 200 system.

The XIO is here and there bridged to PCI-64, using a chip named BRIDGE. The places where it happens include the system board (for the IOC3 multi-I/O chip, two ISP1040B SCSI controllers and RAD1 audio), MENET cards (four IOC3s) and the PCI cage (used for PCI cards in Octane). ARCS is provided as the boot firmware, similar to all contemporary SGI computer systems.

==== CPU ====
The Octane series has single and dual CPU modules. A second CPU cannot be added to a single CPU module, therefore upgrading to two requires replacing the entire CPU module.

What follows is a table of all known models:
{| class="wikitable"
|Processor
|Cache
|Single (Mhz)
|Dual (Mhz)
|-
|R10000SC
|1MB
|175, 195, 225, 250
|175, 195, 225, 250
|-
|R12000SC
|2MB
|270, 300, 400
|270, 300, 400
|-
|R12000SCA
|2MB
|360, 400
|360, 400
|-
|R14000SCA
|2MB
|550, 600
|550, 600
|}

==== Memory ====
The Octane allows 256 MB to 8 GB of system memory, using proprietary 200-pin DIMMs. There are two system board revisions. The first revision (part number 030-0887-00x, usually distinguished by a black handle) only supports 2GB of RAM while the later one (part number 030-1467-001, with a silver handle) supports up to 8GB. The -0887 revision of the mainboard will work with all 32-128 MB DIMMS and the stacked variant of 256MB DIMMS, but not the later single-board version (SGI P/N 9010036). The memory subsystem has vast reserves of bandwidth that can be directly served by the Xbow router to any XIO card.

The Octane's memory controller is aptly named HEART. It acts as a controller between the processor, the memory (SDRAM) and the XIO bus.

==== Graphics ====
Graphics on the Octane are provided by a series of cards: SI, SI+T, SSI, MXI. These are updated XIO versions of Solid Impact (SI), High Impact (SI+T) and Maximum Impact (MXI) from the SGI Indigo2 that were internally designated by SGI as 'MARDIGRAS'. The boards were accelerated and reengineered with faster geometry engine and texture modules to create their new versions: SE, SE+T, SSE, MXE. The SI/SE provides 13.5MB of framebuffer memory while the SSE and MXE have a 27MB framebuffer. The '+T' indicates an additional high speed RDRAM texture board which gives 4MB of texture memory, which is practically indispensable, though quite expensive and fragile. The SI/SE+T has one texture board while the MXI/MXE has 2 texture boards, however, the 2 boards in the MXI/MXE do not double the available texture memory to the system. It just doubles the texture performance.

Later Octanes and Octane 2s support the SGI VPro graphics board series, designated 'ODYSSEY'. The first VPro series cards were the V6 and V8. The main differentiator being that the V6 has 32MB of RAM (unlike the MARDI GRAS option, framebuffer memory and texture memory come from the same pool) and V8 having 128MB. Later, the V10 (32MB) and V12 (128MB) were introduced. The main difference with the new VPro V10/V12 series is that they had double the geometry performance of the older V6/V8. V6 and V10 can have up to 8MB RAM allocated to textures (2X more than the textured-enabled MARDIGRAS options), while V8 and V12 can have up to 108MB RAM used for textures.

The VPro graphics subsystem consists of an SGI proprietary chip set and associated software. The chip set consists of the buzz ASIC, pixel blaster and jammer (PB&amp;J) ASIC, and associated SDRAM.

The buzz ASIC is a single-chip graphics pipeline. It operates at 251 MHz and contains on-chip SRAM. The buzz ASIC has three interfaces:

* Host (16-bit, 400-MHz peer-to-peer XIO link)
* SDRAM (The SDRAM is 32 MB (V6 or V10) or 128 MB (V8 or V12); the memory bus operates at half the speed of the buzz ASIC.)

* PB&amp;J ASIC

As with the MARDIGRAS boards, all VPro boards support OpenGL in hardware (MARDIGRAS is OpenGL 1.1 + SGI Extensions, while VPro upgraded support to OpenGL 1.2) and OpenGL ARB imaging extensions, allowing for hardware acceleration of numerous imaging operations at real-time rates.

Compatibility: The V6/V8 boards require an XBOW 1.3 board, but the V10/V12 boards do appear to require an XBow 1.4 frontplane.

==== I/O and HEART ====
The Octane supports Ultra Wide SCSI devices and has two SCSI controllers. System can have up to three internal 3.5" SCSI SCA devices. Octanes use special mounting sleds for the hard drives which are compatible with Origin 2000, Origin 200 and Onyx2. The system also has external Ultra Wide SCSI bus.

The aptly named HEART is the core of the Octane. It integrates a SDRAM memory controller, a XIO device, an interrupt controller and a processor bus interface for up to four R10000-class processors.

The HEART can be accessed in two ways from the processor. The first one is through the PIU (Programmed I/O Unit) at 0xFF0000 in processor physical address space. The other one is at widget 8 in XIO address space. The only one way available to other XIO devices is through the widget interface, so the Interrupt Status Set register is mapped there at address 0x80.

The HEART contains a SDRAM memory controller with ECC. ECC errors are signaled to the CPUs by interrupts.

The XIO bridge is one of the main functions of the HEART. There are three access windows defined for each XIO widget number. There is a window at 0x10000000+ W*0x1000000 for widget number W, a window at 0x800000000+W*0x80000000 and a window at 0x1000000000+W*0x1000000000.

Note that XIO accesses are deeply pipelined by default. Due to that fact, writing to any XIO widget may not have any effect for several hundred cycles. To guarantee finalization of all posted writes it is required to read the widget flush register.

The XIO bridge in HEART provides also some Flow Control features for two channels. They allow to schedule a hiwater IRQ for any given XIO register address. If the register is an input to a FIFO, as is the case with the IMPACT graphics board, exceeding a prescribed number of writes to this register would cause a FIFO hiwater condition. As you already know, the XIO writes are posted and not immediately executed. Catching the hiwater condition in the HEART and not in the card allows to trap it in a more reliable way.

The HEART interrupt controller is visible from the PIU as a set of registers: interrupt mask registers for all processors (IMR0:3), an interrupt status register (ISR) and ISR clear and set registers that allow atomic manipulation of the ISR.

The XIO side consists of a single register 0x80 that can accept either an atomic ISR bit set command or an atomic ISR bit clear command. These commands cause asserting and deasserting IP7:2 bits in the CPUs whose IMRs contain the bit in question.

A small part of the HEART is a programmable interval timer, consisting of 24-bit COUNT and COMPARE registers. The IRQ can be delivered only to the IP6 bit, which is the highest-priority CPU interrupt except internal CPU timer and HEART error IRQs. The timer counts at 12.5 MHz, every 8th internal HEART cycle (1/4th of the XIO frequency).
[[File:Octane2.jpg|thumb|Another view of an Octane2]]
The HEART controls also the Number In a Can associated with processor modules. It features a standard SGI issue MicroLAN controller. 

=== Octane 2 Upgrades ===
Octane 2 has a revised power supply, system-board and XBOW. Octane 2 also shipped with VPro graphics and supports all available VPro cards (V6, V8, V10 and V12). Later revision Octanes also included some of the improvements mentioned.

The case is blue instead of the green used by the original, the plastics are compatible between the two and the chassis is identical.

=== Operating System Support ===
The Octane was first supported by IRIX version 6.4 with IMPACT or "Mardi Gras" graphics (SI/SSI/MXI and later Enhanced versions). Support for VPro or "Odyssey" graphics in Octanes was introduced with IRIX 6.5.10 for V6/V8, and in IRIX 6.5.11 for V10/V12. (Drivers were released to support V10/V12 under 6.5.10.) All versions of IRIX through 6.5.30 include support for the Octane family machines.</text>
    <sha1>843aeba53f889f8abdb5699e188123add6dda9f8</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:O2 full setup.jpg</title>
  <ns>6</ns>
  <id>71</id>
  <revision>
    <id>79</id>
    <timestamp>2025-02-07T18:41:24Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23" xml:space="preserve">An O2 in a period setup</text>
    <sha1>334681d0aa9470e06e4a6cdc3683aae7a64e2257</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:SGI O2.jpg</title>
  <ns>6</ns>
  <id>72</id>
  <revision>
    <id>80</id>
    <timestamp>2025-02-07T18:42:18Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">An early model O2</text>
    <sha1>eaa848abf61ab2548727ab2ddb84c8ef52e694e3</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:SGI O2+ by Mattst88.jpg</title>
  <ns>6</ns>
  <id>73</id>
  <revision>
    <id>81</id>
    <timestamp>2025-02-07T18:43:03Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24" xml:space="preserve">An O2+ owned by Mattst88</text>
    <sha1>476f398a25a45a2fac607060b557f878c6f00f00</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>O2</title>
  <ns>0</ns>
  <id>74</id>
  <revision>
    <id>82</id>
    <timestamp>2025-02-07T18:43:27Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9475" xml:space="preserve">The Silicon Graphics O2, codename Moosehead, is an entry-level Unix workstation introduced in 1996 by Silicon Graphics, Inc. (SGI) to replace their earlier Indy. Like the Indy, the O2 uses a single MIPS microprocessor and was intended to be used mainly for multimedia. Its larger counterpart was the SGI Octane. The O2 was SGI's last attempt at a low-end workstation.

=== Features ===
O2 features a proprietary high-bandwidth Unified Memory Architecture (UMA) that connects the various system components. The O2 is a highly-integrated system, with CPU, graphics accelerator, memory, SCSI controller, and I/O all incorporated into a single system module, which can be slid out of the chassis with the flip of a lever. A PCI bus is bridged onto the UMA with one expansion slot available. The O2 has a designer case and a modular design, with space for two Ultra SCSI drives mounted on special sleds (only one in the later R10000/R12000 models) and an optional video capture / sound module mounted on the far left side. Further information on the design and construction of the O2 can be found in SGI service manuals on Techpubs. Detailed breakdown pictures and an IRIX hinv dump can be found here.

An O2's unique system ID (MAC address) is stored on the small PCI riser card that connects the PCI card holder to the motherboard. If this riser card is swapped, the corresponding black plastic badge on the rear of the case should be swapped as well to preserve consistency.

WARNING: The O2 system module should NEVER be removed or installed while the power cord is connected. Doing so can permanently damage the motherboard.

==== CPU ====
The O2 comes in two distinct CPU flavours; the low-end MIPS 180 to 350 MHz R5000- or RM7000-based units and the higher-end 150 to 400 MHz R10000- or R12000-based units. The 200 MHz R5000 CPUs with 1 MB L2-cache are generally noticeably faster than the 180 MHz R5000s with only 512 KB cache. There is a hobbyist project that has successfully retrofitted a 600 MHz RM7xxx MIPS processor into the O2.

There is also a hobbyist project that has successfully retrofitted a 600 MHz R7000 MIPS processor into the O2. In theory faster CPUs at 900MHz any beyond are possible, but this would require the public release of the O2 PROM source code which at present is not available and probably never will be.
[[File:O2 full setup.jpg|thumb|An O2 in full setup]]
A recall of some early versions of the RM7000A 350Mhz CPU is thought to have hastened the removal of the O2 from SGI's product line.

==== Memory ====
There are eight DIMM slots on the motherboard and memory on all O2s is expandable to 1 GB using proprietary 239-pin SDRAM DIMMs. The Memory &amp; Rendering Engine (MRE) ASIC contains the memory controller. Memory is accessed via a 133 MHz 144-bit bus, of which 128 bits are for data and the remaining for error-correcting code (ECC). This bus is interfaced by a set of buffers to the 66 MHz 256-bit memory system.

Original SGI-branded O2 DIMMs are either single-sided (SS) with memory chips on only one side of the module or double-sided (DS), and are color-coded to assist in identification. 3rd party DIMMs may or may not follow these conventions. Knowing the current memory configuration is important as DIMMs must be installed according to a number of specific rules.

* The DIMMs in slots 1 and 2 make up Bank A. DIMMs in slots 3 and 4 make up Bank B, and so on.
* A bank of two slots must have a DIMM in each slot or be empty (except for slots 1 and 2, Bank A, which must always be populated.)
* The two DIMMs in any bank must be of the same size and type.
* The largest size DIMMs must be in Bank A.
* DIMM banks must be filled sequentially, beginning with bank A.
* Equal or smaller size DIMMs must be in Bank B, and so on.
* Do not skip banks, or the memory will not be recognized.

To install high density (128 MB) DIMMs, PROM revision 4.4 or higher is required. With older PROM revisions maximum memory is 256 MB. For IRIX 6.3 there are patches to upgrade the PROM as described in "Silicon Graphics® O2® Workstation Memory Installation Instructions", for IRIX 6.5 PROM images come with the operating system and overlays CD sets.

==== Graphics ====
[[File:SGI O2.jpg|left|thumb|An early-model O2 with the original cube logo]]
The CRM chipset that SGI developed for the O2 shares OpenGL calculations with the CPU. Due to the unified memory architecture, video memory is shared with main memory, and there is effectively an 'unlimited' amount of texture memory. Another useful feature is that any incoming video data from the Audio/Video option can be mapped directly as an OpenGL texture without having to perform a copy or move.

ICE (Image Compression Engine — a dedicated 64-bit R4000-based processor containing a 128-bit SIMD unit running at 66 MHz, which is used to accelerate various image and video operations)

The O2 Video system supports two simultaneous input video streams and one output video stream which can be separated into two outputs, one carrying pixel information, the other carrying alpha (key) information.

Using the O2 Video system, it is possible to capture live video into the computer's memory which can then be displayed in a graphics window on the screen or further processed by an application. It is also possible to generate video output from images in memory, which can be displayed on a standard video monitor, or recorded to a VTR. Using the VL programming library, a program can capture video in either the RGB or YCrCb color spaces, and either full or reduced size formats, and in a format usable for input to the compressor/decompressor, display on the graphics screen, or as an input to a graphics processing and/or texture operation.

SGI offered two video options for the O2/O2+: the AV1 interface and the AV2 interface.

The AV1 interface supports Composite and S-Video (Y/C) (both analog), and Digital I/O via the Camera/Digital Video port. The analog I/O jacks are for use with standard analog video equipment, supporting both PAL and NTSC video formats. There are a variety of controls available that allow the user or programmer to set various parameters used for the decoding and encoding of the video signals. The digital input of the AV1 is for use with the O2Cam Digital System Camera, or can be connected to an optional digital video input and output adapter to interface to standard SMPTE259M serial digital video devices.

The AV2 interface supports two ITU-601 (CCIR-601) serial digital video input connectors and two similar output connectors, as well as GPI input and output and analog (black burst) sync input and loop through.

==== I/O ====
I/O functionality is provided by the IO Engine ASIC. The ASIC provides a 33-bit PCI-X bus, an ISA bus, two PS/2 ports for keyboard and mouse, and a 10/100 Base-T Ethernet port. The PCI-X bus has one slot, but the ISA bus was present solely for attaching a Super I/O chip to provide serial and parallel ports.

=== O2+ ===
[[File:SGI O2+ by Mattst88.jpg|thumb|An O2+, property of mattst88]]
The O2+ is a special variant of the SGI O2 with a purple/grey color scheme, top of the line multimedia, CPU and memory. It was produced in very low quantities and has remained a valuable item for collectors, selling for many times the going rate for O2s on average.

=== Operating System Support ===
IRIX versions 6.3 and 6.5 (up to the latest overlay - 6.5.30) are supported on this machine, however, only in 32-bit mode, due to the nature of the O2's internal architecture. For CPU-specific versions, see also: IRIX for O2.

Besides the default CD-based Installation, the O2 also supports network installation.

=== Hardware Problems ===
The Toshiba CD-ROM drives in the O2 commonly throw a small white plastic gear from the tray motor. Symptoms include the tray either refusing to open or refusing to stay closed. This problem is relatively easy to fix by opening the CD-ROM drive and pushing the gear back onto the motor shaft, then adding a small amount of glue to keep the gear in place. To avoid damaging the tray mechanism during ordinary use, do not push it closed: use the "inject" command instead.

To quote kjaer in a Nekochan forum post &lt;nowiki&gt;https://web.archive.org/web/20170821000034/http://forums.nekochan.net/viewtopic.php?f=3&amp;t=16726667&lt;/nowiki&gt; "...there is a pressfit nylon pinion on the transport motor that opens and closes the drive tray, and also raises and lowers the optical pickup assembly (moves it closer to the disc after the tray closes, and moves it away from the disk before the tray opens). This pinion splits when it ages, and when this happens the static friction between pinion and spindle is no longer sufficient to hold the torque required to lift the optical pickup. The drive interprets this as a mis-load and ejects the tray." A further discussion with images can be found &lt;nowiki&gt;https://web.archive.org/web/20170820231441/http://forums.nekochan.net/viewtopic.php?f=3&amp;t=16727779#p7360973&lt;/nowiki&gt;

==== Memory ====
The O2's proprietary memory modules are highly susceptible to dirt and shock, particularly during shipping. The symptoms of a bad memory contact include random memory errors and a total inability to boot, with a solid red or blinking amber LED at startup. Careful cleaning and re-seating of memory will typically solve such problems, though the DIMMs should also be carefully inspected for missing surface-mount components, which can be easily knocked-off via mishandling.</text>
    <sha1>8b9261fbd9d0ad2d88271095ef3cccff0ad66fa5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Origin 3000 Rack Cluster.jpg</title>
  <ns>6</ns>
  <id>75</id>
  <revision>
    <id>83</id>
    <timestamp>2025-02-07T18:45:57Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="27" xml:space="preserve">An Origin 3000 Rack cluster</text>
    <sha1>266e8c13397ec965eff376978242cb8f49eb31e6</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Comparison of the O2k to the O3k.jpg</title>
  <ns>6</ns>
  <id>76</id>
  <revision>
    <id>84</id>
    <timestamp>2025-02-07T18:46:38Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="51" xml:space="preserve">Origin 3000 and Origin 2000 side by side comparison</text>
    <sha1>4129baaef4ee6e38e65142a05fbec7aabc298f0f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Origin 3000 Full Rack.jpg</title>
  <ns>6</ns>
  <id>77</id>
  <revision>
    <id>85</id>
    <timestamp>2025-02-07T18:47:29Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">A full O3000 rack</text>
    <sha1>f741c118699f3e5f1b755c066f294e0b8e22b60f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:G-Brick.jpg</title>
  <ns>6</ns>
  <id>78</id>
  <revision>
    <id>86</id>
    <timestamp>2025-02-07T18:48:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7" xml:space="preserve">G-Brick</text>
    <sha1>2181b4db1424a9353451d46f7273993a0ce99352</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Origin 3000</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>87</id>
    <timestamp>2025-02-07T18:48:51Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Origin 3000 Rack Cluster.jpg|thumb|An Origin 3000 Rack cluster]] The SGI Origin 3000, is the successor of the SGI Origin 2000 line. Unlike previous versions, it did not offer a deskside version, opting for full and half rack configurations instead. It also introduced the "brick" architecture used by many Chimera architecture SGIs.  === Features === Physically, the Origin 3000 is based on "bricks" - rackmounted modules that provide a specific function, that are con..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6456" xml:space="preserve">[[File:Origin 3000 Rack Cluster.jpg|thumb|An Origin 3000 Rack cluster]]
The SGI Origin 3000, is the successor of the SGI Origin 2000 line. Unlike previous versions, it did not offer a deskside version, opting for full and half rack configurations instead. It also introduced the "brick" architecture used by many Chimera architecture SGIs.

=== Features ===
Physically, the Origin 3000 is based on "bricks" - rackmounted modules that provide a specific function, that are connected together using NUMAlink 3 cables for modules providing compute functions, or Crosstown2 cables for modules providing I/O functions. These bricks are mounted in a standard 19-inch rack. There are two racks for the Origin 3000, a 17U-high half rack, and a 39U-high tall rack. Architecturally, the Origin 3000 is based on the distributed shared memory NUMAflex architecture. The NUMAlink 3 system interconnect uses a fat tree hypercube network topology.

The following table shows a list of models and their possible configurations:
{| class="wikitable"
|Model
|CPUs
|Memory
|Chassis
|-
|Origin 3200
|2 to 8
|Up to 16 GB
|Half Rack
|-
|Origin 3400
|4 to 32
|Up to 16 GB
|1 Full Rack
|-
|Origin 3800
|16 to 512
|Up to 1 TB
|1-16 Full Racks
|-
|Origin 3900
|4 to 512
|Up to 1 TB
|1 to 4 Full Racks
|}

==== C-Brick ====
[[File:Comparison of the O2k to the O3k.jpg|left|thumb|Comparison of the Origin 2000 and Origin 3000, side-by-side]]
The C-Brick (Compute Brick) is a 3U-high enclosure that contains CPUs on a PCB. The node contains two or four processors, the local and directory memory, and the Bedrock ASIC. The two processors and their secondary caches is contained on a PIMM (Processor Integrated Memory Module) daughter card that plugs into two 240-pin connectors on the node board. Initially, the Origin 3000 used the 360 MHz R12000 and the 400 MHz R12000A processors with 4 or 8 MB of secondary cache. In May 2001, the 500 MHz R14000 was introduced with 8 MB of secondary cache and in February 2002, the 600 MHz R14000A was made available. Near the end of its lifetime, the C-Brick was updated with 800 MHz MIPS processors.

==== CX-Brick ====
[[File:Origin 3000 Full Rack.jpg|thumb|An Origin 3000 Rack]]
The CX-Brick is a 4U-high enclosure that is only used in Origin 3900 and Onyx 3900 systems. It differs from the C-Brick by containing four node boards and eight-port router ASIC. The CX-Brick can support up to 16 processors and 32 GB of memory. The CX-Brick initially used the IP53 motherboard that supported 500 MHz R14000 and 600 MHz R14000A processors with 8 MB secondary caches, later upgraded to use the R16000 and R16000A. It connects to the system using NUMAlink 3.

=== R-Brick ===
The R-Brick (Router Brick) is a 2U-high enclosure that features an eight-port router ASIC. Its purpose is to route NUMAlink packets throughout the system to connect the C-Bricks together. R-bricks for the Origin 3400 have a router ASIC with two ports disabled to prevent them from being upgraded into Origin 3800 systems.

=== I-Brick ===
The I-Brick is a 4U-high enclosure that provides boot I/O functions for the Origin 3000. It features five hot swappable PCI-X slots, with three clocked at 33 MHz and two at 66 MHz on two separate buses, two sled-mounted 3.5-inch Fibre Channel hard drives and a proprietary CD-ROM drive. The I-Brick also provides a 10/100BASE-T Ethernet port, an IEEE-1394 port, a serial port, two USB ports as well as a real time clock and NVRAM for storing configuration information through the IO9. It connects to the system using Crosstown2.

==== IX-Brick ====
The IX-Brick is a 4U-high enclosure that is only used in Origin 3900 and Onyx 3900 systems. It an updated version of the I-brick with 133 MHz PCI-X expansion slots. It connects to the system using Crosstown2 cables.

=== V-Brick ===
The V-brick is a 4U-high enclosure that supports two InfinitePerformance (Commercial name for VPro/Odyssey Graphics) graphics pipes. Each graphics pipe consists of a 128 MB SGI VPro V12 graphics card. The V-brick connects to the system using Crosstown2 cables. This was one of two options for graphics.

=== G-Brick ===
The G-brick is a 18U-high enclosure that supports the InfiniteReality graphics subsystem. Each G-brick can support two InfiniteReality3 or InfiniteReality4 graphics pipes, although only one pipe can have four raster manager boards while the other can have two. The G-brick connects to the system using Crosstown2 cables.

==== Other Bricks ====
[[File:G-Brick.jpg|thumb|An Origin 3000 G-brick]]
Some systems were offered with D, P, PX and X Bricks. D is for data, and contains Fibre Channel, P and PX are PCI-X peripheral bricks, and X is an XIO brick.

=== Memory ===
The C-Brick supports 512 MB to 8 GB of local memory through eight DIMM slots organised into eight banks by using proprietary 100 MHz ECC DDR SDRAM DIMMs with capacities of 256 MB, 512 MB and 1 GB. The data path between the DIMM and the Bedrock ASIC is 144 bits wide, with 128 bits for data and 16 bits for ECC. Because the Origin 3000 uses a distributed shared memory model, directory memory is used to maintain cache coherency between the processors. Unlike the Origin 2000, which requires dedicated proprietary DIMMs for the directory memory, the Origin 3000's directory memory is integrated in the same DIMMs that contain the local memory. Due to this, there are two kinds of DIMM used in the Origin 3000: standard DIMMs, which supports systems with up to 128 processors, and premium DIMMs, which supports systems with more than 128 processors. The 256 MB DIMM is a standard DIMM, the 1 GB DIMM is a premium DIMM and the 512 MB DIMM can be either.

=== Power Supply ===
The Origin 3000 uses a "Power Bay" that contains up to 6 hot swappable powersupplies and provides the Bricks of the system with power (48VDC). It is connected to a wall outlet using a Power Distribution Unit. For this reason, most configurations require 240V. The 3400 and 3800 configurations had alternative setups for power.

=== L2 and L3 Controllers ===
The L2 and L3 Controllers are control systems used to manage the status of each brick in the system and to issue commands, monitor the environment and more. The L2 controller is a small Linux-based silver box that runs Linux on an embedded PowerPC system. The L3 controller was a Linux-based console that could manage several L2 systems.

=== Operating System Support ===
IRIX Versions from 6.5.15 to 6.5.30 supports the Origin 3000.</text>
    <sha1>87ebf8136c6782263ec60710fb430d2846242cb4</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>88</id>
    <parentid>34</parentid>
    <timestamp>2025-02-07T18:51:50Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Updated Software Category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2879" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				• [[IRIX 101]]&lt;/div&gt;• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====


===== GL2 Versions =====


===== Development Information =====


===== Open Source Distributions =====
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>00f90259b9cf9266050416e574bc39cecdd263c6</sha1>
  </revision>
  <revision>
    <id>102</id>
    <parentid>88</parentid>
    <timestamp>2025-02-08T04:05:34Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2899" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				• [[IRIX 101]]&lt;/div&gt;• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx|Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====


===== GL2 Versions =====


===== Development Information =====


===== Open Source Distributions =====
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>c660651219ff4b502f1a220db5a0bb0ec8078638</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>IRIX 6.5</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>89</id>
    <timestamp>2025-02-07T19:08:58Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "IRIX 6.5 is the final major version of IRIX released first in 1998. Further incremental improvements were made from 1998 to 2006, with security updates ending in 2013 under Rackable Systems.   ==== Improvements over IRIX 6.2 ==== IRIX 6.5's most notable improvement is standardized distribution. No more is a specific IRIX version needed for a specific machine. It includes support for all 64-bit capable SGIs with a few exceptions (e.g. the Crimson).   ====== New Features:..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1558" xml:space="preserve">IRIX 6.5 is the final major version of IRIX released first in 1998. Further incremental improvements were made from 1998 to 2006, with security updates ending in 2013 under Rackable Systems. 

==== Improvements over IRIX 6.2 ====
IRIX 6.5's most notable improvement is standardized distribution. No more is a specific IRIX version needed for a specific machine. It includes support for all 64-bit capable SGIs with a few exceptions (e.g. the Crimson). 

====== New Features: ======

* OpenGL 1.1 support for all systems supported. 
* Desktop now called IRIX Interactive Desktop
* Improved security for remote X and other subsystems (safer defaults)
* Gigabit support
* Improved C library support. Compiler now supports C99. 
* MIPSPro replaces IDO/uopt as the main compiler backend.
* Later versions have Firewire and USB support.
* Later versions added OpenGL 1.2 support

==== Lifecycle ====
From 1998 to 2006 a new point release was released every quarter from .1 to .30. Security updates continued for 6.5.22 and higher until 2013. Shortly thereafter, SGI's Supportfolio site went offline. 

==== System Support ====
IRIX 6.5 through .22 supported all of the following systems:

* [[IRIS Indigo]] R4000
* [[Onyx|Onyx/Challenge R4000-R10000]]
* [[Indy]]
* [[Indigo2]]
* [[Onyx2]]
* [[Octane]]
* [[Origin 2000|Origin 2000 and 200]]
* [[Challenge S]]
* [[O2]]
* [[Fuel]]
* [[Origin 300]]
* [[Origin 350]]
* [[Origin 3000]]
* [[Tezro]]
* [[Onyx4]]

After 6.5.22, support for the following systems was dropped:

* IRIS Indigo
* Indy
* Indigo2
* Onyx/Challenge</text>
    <sha1>130a26d2e3ed3014b5b9d5901549236544d3ff4d</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>IRIX 6.2</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>90</id>
    <timestamp>2025-02-08T02:48:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "IRIX 6.2 was released in early 1996 for multiple SGI desktops. The 6.x series is based on late 5.x code with 64-bit support in the OS being its major killer app. IRIX 6.3 and 6.4 are special releases of 6.2 for the O2 and Octane, Origin2000/Onyx2 and Origin 200.   ==== Changes ====  * 64-bit kernel support and the new n32 ABI.  * Removal of all 32-bit only IRIX platforms from the supported list (i.e. R2000 and R3000 systems).  * Improved system stability.  * XFS file sys..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="657" xml:space="preserve">IRIX 6.2 was released in early 1996 for multiple SGI desktops. The 6.x series is based on late 5.x code with 64-bit support in the OS being its major killer app. IRIX 6.3 and 6.4 are special releases of 6.2 for the O2 and Octane, Origin2000/Onyx2 and Origin 200. 

==== Changes ====

* 64-bit kernel support and the new n32 ABI. 
* Removal of all 32-bit only IRIX platforms from the supported list (i.e. R2000 and R3000 systems). 
* Improved system stability. 
* XFS file system is default. EFS no longer supported for system installs. 
* VNode/VFS system imported, enabling new filesystems to be more easily added. 
* COFF applications no longer supported.</text>
    <sha1>478d9619acbf24af25637eaecdbcde9bc0d88d41</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>IRIX 5.3</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>91</id>
    <timestamp>2025-02-08T02:59:38Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "IRIX 5.3 was released in November of 1994, the last of the IRIX 5.x series that began in March of 1993. IRIX 5.3 improved system stability and introduced many features of IRIX such as XFS (with the XFS release in 12/1994), ELF executables and more."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="248" xml:space="preserve">IRIX 5.3 was released in November of 1994, the last of the IRIX 5.x series that began in March of 1993. IRIX 5.3 improved system stability and introduced many features of IRIX such as XFS (with the XFS release in 12/1994), ELF executables and more.</text>
    <sha1>db1760b6ccb5fae17778e6e7f08d66e68159105f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>IRIX 4.0</title>
  <ns>0</ns>
  <id>83</id>
  <revision>
    <id>92</id>
    <timestamp>2025-02-08T03:03:32Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "IRIX 4.0, introduced in September of 1991 with the IRIS Indigo workstation was the first version of IRIX to be officially named "IRIX." Replacing the [[4Sight]] NeWS-based system, X11R4 using the IRIS Desktop (later called IRIX Interactive Desktop), and was the first version to be released on CD, as opposed to QIC tape."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="321" xml:space="preserve">IRIX 4.0, introduced in September of 1991 with the IRIS Indigo workstation was the first version of IRIX to be officially named "IRIX." Replacing the [[4Sight]] NeWS-based system, X11R4 using the IRIS Desktop (later called IRIX Interactive Desktop), and was the first version to be released on CD, as opposed to QIC tape.</text>
    <sha1>5873cc9f04a960cc92fc60a95d49c3393c25670e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Powerseries-1201-front.jpg</title>
  <ns>6</ns>
  <id>84</id>
  <revision>
    <id>93</id>
    <timestamp>2025-02-08T03:39:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>PowerSeries Deskside Unit owned by Gerhard Lernerz</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="64" xml:space="preserve">== Summary ==
PowerSeries Deskside Unit owned by Gerhard Lernerz</text>
    <sha1>c241ac685aebb29c0e1886204d5745d8efad97e5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:4d380 rack.jpg</title>
  <ns>6</ns>
  <id>85</id>
  <revision>
    <id>94</id>
    <timestamp>2025-02-08T03:56:57Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>PowerSeries Rack Unit owned by Jan Jaap</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="53" xml:space="preserve">== Summary ==
PowerSeries Rack Unit owned by Jan Jaap</text>
    <sha1>497449235be86eed237c92656bcf761e5b3d3d48</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>MediaWiki:Licenses</title>
  <ns>8</ns>
  <id>86</id>
  <revision>
    <id>95</id>
    <timestamp>2025-02-08T03:57:42Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "- PD|PD: public domain CC-by-sa-2.5|Creative Commons Attribution ShareAlike 2.5"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="79" xml:space="preserve">-
PD|PD: public domain
CC-by-sa-2.5|Creative Commons Attribution ShareAlike 2.5</text>
    <sha1>2b223913032253d497c86773c011aa7e49133285</sha1>
  </revision>
  <revision>
    <id>96</id>
    <parentid>95</parentid>
    <timestamp>2025-02-08T03:57:58Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="78" xml:space="preserve">PD|PD: public domain

CC-by-sa-2.5|Creative Commons Attribution ShareAlike 2.5</text>
    <sha1>a867319284afda83f28975bb5e635a824e0ba075</sha1>
  </revision>
  <revision>
    <id>98</id>
    <parentid>96</parentid>
    <timestamp>2025-02-08T04:00:14Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Base setup</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="186" xml:space="preserve">* Free licenses:
** PD|PD: public domain
** CC-SA|Creative Commons Attribution ShareAlike 2.5 
** CC-SA-NC|Creative Commons Attribution Share Alike Non-Commercial 2.5
** MIT| MIT License</text>
    <sha1>14024ad56da2a4b4b1ff635a346a28ba1f1685a1</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:4d380 open rack.jpeg</title>
  <ns>6</ns>
  <id>87</id>
  <revision>
    <id>97</id>
    <timestamp>2025-02-08T03:58:40Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Open PowerSeries Rack Unit owned by Jan Jaap</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="58" xml:space="preserve">== Summary ==
Open PowerSeries Rack Unit owned by Jan Jaap</text>
    <sha1>1b64ffb730fcd1f187eaa8ec680c47de2b9658fa</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:PowerSeries Twin.jpg</title>
  <ns>6</ns>
  <id>88</id>
  <revision>
    <id>99</id>
    <timestamp>2025-02-08T04:02:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Twin Tower style PowerSeries</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="65" xml:space="preserve">== Summary ==
Twin Tower style PowerSeries
== Licensing ==
{{PD}}</text>
    <sha1>5d2745aeb46778a10a63a5dfe57ad85fad024019</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-07 03:20:10+00|53">
  <title>File:Onyx2 rack.jpg</title>
  <ns>6</ns>
  <id>89</id>
  <revision>
    <id>100</id>
    <timestamp>2025-02-08T04:04:21Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10" xml:space="preserve">Onyx2 Rack</text>
    <sha1>5003957ea228b2aba4b6e5fb3155c3c48fdd8337</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>103</id>
    <parentid>102</parentid>
    <timestamp>2025-02-08T04:06:18Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2894" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				• [[IRIX 101]]&lt;/div&gt;• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====


===== GL2 Versions =====


===== Development Information =====


===== Open Source Distributions =====
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>d4ca3fc479b482435ad011184be71ecab3259593</sha1>
  </revision>
  <revision>
    <id>110</id>
    <parentid>103</parentid>
    <timestamp>2025-02-08T04:15:17Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Development Information */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3010" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				• [[IRIX 101]]&lt;/div&gt;• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====


===== GL2 Versions =====


===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

•  [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

===== Open Source Distributions =====
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>7b924365825113586287641b71b35ee206f9a79b</sha1>
  </revision>
  <revision>
    <id>111</id>
    <parentid>110</parentid>
    <timestamp>2025-02-08T04:16:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3031" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					
				• [[IRIX 101]]&lt;/div&gt;• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====


===== GL2 Versions =====


===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

•  [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

===== Open Source Distributions =====
• [[SGI Freeware]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>a30e78e91546cdbe8834dfad47b7e92975179483</sha1>
  </revision>
  <revision>
    <id>113</id>
    <parentid>111</parentid>
    <timestamp>2025-02-08T04:36:21Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3154" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]
• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====


===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

•  [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>3986914274d3734aa38b7ee480eed15573a98305</sha1>
  </revision>
  <revision>
    <id>114</id>
    <parentid>113</parentid>
    <timestamp>2025-02-08T04:38:13Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* RISC/OS */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3165" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]
• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• RISC/OS
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

•  [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>c85e659548ac2dd3ebc0f2bd1c8307c8cced8b6d</sha1>
  </revision>
  <revision>
    <id>115</id>
    <parentid>114</parentid>
    <timestamp>2025-02-08T04:38:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* RISC/OS */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3169" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]
• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

•  [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>d137dcd11001b7a9e3ae64df5fef0a6b62952a9e</sha1>
  </revision>
  <revision>
    <id>117</id>
    <parentid>115</parentid>
    <timestamp>2025-02-08T04:41:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3170" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

•  [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>c3d135f2009ca43a7681152aed33bd9e439f67cc</sha1>
  </revision>
  <revision>
    <id>121</id>
    <parentid>117</parentid>
    <timestamp>2025-02-10T17:57:49Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3278" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

•  [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>fabd4a5826688531a061921f5ce88f8be1a1608e</sha1>
  </revision>
  <revision>
    <id>123</id>
    <parentid>121</parentid>
    <timestamp>2025-02-12T02:50:51Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Development Information */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3290" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''[[News]]''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>5e1af9996527a2e4ac8b91e2353d2b498f936047</sha1>
  </revision>
  <revision>
    <id>126</id>
    <parentid>123</parentid>
    <timestamp>2025-02-16T16:27:12Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3286" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>c10c7d86494e94165e2321f604e863bbaa7e14ef</sha1>
  </revision>
  <revision>
    <id>127</id>
    <parentid>126</parentid>
    <timestamp>2025-02-16T17:12:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3546" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Cat 5''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>3687f90de84b12b8b5cd0534a3e8e552fe34223e</sha1>
  </revision>
  <revision>
    <id>132</id>
    <parentid>127</parentid>
    <timestamp>2025-02-16T19:11:50Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3560" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>0311e813e07af2d2f432f780aa125cb7e21fd0f5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>File:Onyx2 Late Logo.jpg</title>
  <ns>6</ns>
  <id>90</id>
  <revision>
    <id>104</id>
    <timestamp>2025-02-08T04:09:27Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="31" xml:space="preserve">Onyx2 with the later logo font.</text>
    <sha1>668dab16e3d1d6411bc5a03c16d9fc9089c56d15</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>File:Onyx2-raion-passionlip.jpg</title>
  <ns>6</ns>
  <id>91</id>
  <revision>
    <id>105</id>
    <timestamp>2025-02-08T04:10:29Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="40" xml:space="preserve">An older model Onyx2 with the cube skins</text>
    <sha1>38200af8a48934a9f3143904bd7ec63823589cc7</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>File:Onyx2-rear.jpg</title>
  <ns>6</ns>
  <id>92</id>
  <revision>
    <id>106</id>
    <timestamp>2025-02-08T04:11:29Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38" xml:space="preserve">Rear of an Onyx2, minimally configured</text>
    <sha1>a0fc51f045b44139810cb145e7e4947e51218d58</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Onyx2</title>
  <ns>0</ns>
  <id>93</id>
  <revision>
    <id>107</id>
    <timestamp>2025-02-08T04:11:52Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6557" xml:space="preserve">[[File:Onyx2 Late Logo.jpg|thumb|An onyx2 with the later font]]
For the rack variant, see the [[Origin 2000]] article

The SGI Onyx2, code name ''Kego'', is the successor of the SGI Onyx. The Onyx2's basic system architecture is based on the Origin 2000, but the midplane and some parts such as the IO6 are different between models. The Onyx2 is notable for the InfiniteReality2, 2E and 3 boards it usually is equipped with, as well as its imposing size, weight and aesthetics.

=== Features ===
The Onyx2 deskside form factor can handle up to 4 CPUs distributed across two nodeboards, a maximum of 4 GB of RAM, one GE-16-4, a single DG5-8 for up to 8 displays, and two IR3 or IR4 raster managers for a maximum of 512 MB and 2 GB respectively of texture memory, and can support up to two users simultaneously out of the box. Possibly more with a CADDUO card installed.

A 3-slot PCI cage can be installed as well as a maximum of 10 XIO cards, giving a massive amount of expandability. This is in addition to 5 hard disks and one 5.25 option drive.

==== CPU ====
The following table shows the possible CPU configurations.
{| class="wikitable"
|Processor
|Clockspeed
| colspan="4" |Cache
|-
|R10000
|180 MHz
|1MB
| colspan="3" |R10000
|-
|R10000
|195 MHz
|4MB
| colspan="3" |R10000
|-
|R10000
|250 MHz
|4MB
| colspan="3" |R10000
|-
|R12000
|300 MHz
|8MB
| colspan="3" |R12000
|-
|R12000
|350 MHz
|4MB
| colspan="3" |R12000
|-
|R12000
|400 MHz
|8MB
| colspan="3" |R12000
|-
|R14000
|500 MHz
|8MB
| colspan="3" |R12000
|}

==== InfiniteReality ====
The Onyx2 can handle the following revisions of the InfiniteReality:
{| class="wikitable"
|Model
|GE Revision
|Raster Manager
|Display Generator
|Texture RAM (MB)
|Raster RAM (MB)
|-
|InfiniteReality2
|GE14-4
|RM7-16 or RM7-64
|DG5-2 or DG5-8
|16 to 32
|80 to 160
|-
|Reality
|GE14-2
|RM8-16 or RM8-64
|DG5-2 or DG5-8
|16 to 64
|40 to 80
|-
|InfiniteReality2E
|GE16-4
|RM9-64
|DG5-2 or DG5-8
|64 to 128
|80 to 160
|-
|InfiniteReality3
|GE16-4
|RM10-256
|DG5-2 or DG5-8
|256 to 512
|80 to 160
|-
|InfiniteReality4
|GE16-4
|RM11-1024
|DG5-2 or DG5-8
|1,024 to 2048
|2,560 to 5,120
|}
[[File:Onyx2-raion-passionlip.jpg|left|thumb|An Onyx2 owned by Raion with the cube logo. ]]


InfiniteReality2 is how hinv refers to an InfiniteReality that is used in the Onyx2. The InfiniteReality2 however, was still marketed as the InfiniteReality. It is the second implementation of the InfiniteReality architecture, and was introduced in late 1996. It is identical to the InfiniteReality architecturally, but differs mechanically as the Onyx2's Origin 2000-based card cage is different from the Onyx's Challenge-based card cage.

The Reality is a cost-reduced version of the InfiniteReality2 intended to provide similar performance. Instead of using the GE14-4 Geometry Engine board and the RM7-16 or RM7-64 Raster Manager boards, the Reality uses the GE14-2 Geometry Engine board and the RM8-16 or RM8-64 Raster Manager boards. The GE14-2 has two Geometry Engine Processors, instead of four like the other models. The RM8-16 and RM864 has 16 or 64 MB of texture memory respectively and 40 MB of raster memory. The Reality was also limited by the number of Raster Manager boards it could support, one or two. When maximally configured with two RM8-64 Raster Manager boards, the Reality pipeline has 80 MB of raster memory.

The InfiniteReality2E is an upgrade of the InfiniteReality, marketed as the InfiniteReality2, introduced in 1998. It succeeded the InfiniteReality board set and was itself succeeded by the InfiniteReality3 in 2000, but was not discontinued until 10 April 2001.

It improves upon the InfiniteReality by replacing the GE14-4 Geometry Engine board with the GE16-4 Geometry Engine board and the RM7-16 or RM7-64 Raster Manager boards with the RM9-64 Raster Manager board. The new Geometry Engine board operated at 112 MHz, improving geometry and image processing performance. The new Raster Manager board operated at 72 MHz, improving anti-aliased pixel fill performance.

InfiniteReality3 is the next upgrade and one of the most common for the Onyx2 and Onyx3000 on the secondhand market. The only improvement over the previous implementation is replacement of the RM9-64 Raster Manager with the RM10-256 Raster Manager, which has 256 MB of texture memory, four times that of the previous raster manager.

InfiniteReality4 is the ultimate iteration, introduced in 2002. Primarily used on the Onyx3000 and Onyx350 "G-Bricks". The only improvement over the previous implementation is the replacement of the RM10-256 Raster Manager by the RM11-1024 Raster Manager, which has improved performance, 1 GB of texture memory and 2.5 GB of raster memory, four and thirty-two times that of the previous raster manager, respectively.

Below is a performance table offering comparisons:
{| class="wikitable"
|Reality
|5.5
|94 to 188
| colspan="3" |100 to 200
|-
|InfiniteReality2E
|13.1 to 210
|192 to 6,100
| colspan="3" |200 to 6,400
|-
|InfiniteReality3
|13.1 to 210
|5,600
| colspan="3" |6,400
|-
|InfiniteReality4
|13.1 to 210
|10,200
| colspan="3" |6,400
|}
[[File:Onyx2-rear.jpg|thumb|Rear of an Onyx2, minimally configured]]

==== Memory ====
DIMMs are available in sizes of 16, 32, 64 and 256 MB. The memory modules used in the Origin 200 and Origin 2000 / Onyx 2 are of the same type. To support the Origin 2000 distributed shared memory model, the memory modules are proprietary and include directory memory, which contains information on the contents of remote caches for maintaining cache coherency, supporting up to 32 processors. Additional directory memory is required in configurations with more than 32 processors. The additional directory memory is contained on proprietary DIMMs that are inserted into eight DIMM slots set aside for its use.

==== IO6G ====
An IO6G base I/O board is present in every system. It is a XIO card that provides:

* a 10/100BASE-TX Ethernet port
* 2 sets of PS/2 ports
* 4 Serial ports provided by dual UARTs
* 1 internal Fast 20 UltraSCSI single-ended port
* 1 external wide UltraSCSI, singled ended port
* 1 real-time interrupt output for frame sync
* 1 real-time interrupt input (edge triggered)

Also on the card is the Flash PROM, NVRAM and real time clock of the system.

==== PCI ====
The system can utilize PCI with the addition of an Origin 2000 XIO PCI "Shoebox" or individual XTalk PCI adapters inserted in the cage. These are the same sort form factor as Octane units.

=== Operating System Support ===
IRIX Versions from 6.4 to 6.5.30 supported the Onyx2</text>
    <sha1>5551088d2c7397287f5a36f7da82b60020dd6825</sha1>
  </revision>
  <revision>
    <id>148</id>
    <parentid>107</parentid>
    <timestamp>2025-02-16T21:12:36Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6580" xml:space="preserve">[[File:Onyx2 Late Logo.jpg|thumb|An onyx2 with the later font]]
For the rack variant, see the [[Origin 2000]] article

The SGI Onyx2, code name ''Kego'', is the successor of the SGI Onyx. The Onyx2's basic system architecture is based on the Origin 2000, but the midplane and some parts such as the IO6 are different between models. The Onyx2 is notable for the InfiniteReality2, 2E and 3 boards it usually is equipped with, as well as its imposing size, weight and aesthetics.

=== Features ===
The Onyx2 deskside form factor can handle up to 4 CPUs distributed across two nodeboards, a maximum of 4 GB of RAM, one GE-16-4, a single DG5-8 for up to 8 displays, and two IR3 or IR4 raster managers for a maximum of 512 MB and 2 GB respectively of texture memory, and can support up to two users simultaneously out of the box. Possibly more with a CADDUO card installed.

A 3-slot PCI cage can be installed as well as a maximum of 10 XIO cards, giving a massive amount of expandability. This is in addition to 5 hard disks and one 5.25 option drive.

==== CPU ====
The following table shows the possible CPU configurations.
{| class="wikitable"
|Processor
|Clockspeed
| colspan="4" |Cache
|-
|R10000
|180 MHz
|1MB
| colspan="3" |R10000
|-
|R10000
|195 MHz
|4MB
| colspan="3" |R10000
|-
|R10000
|250 MHz
|4MB
| colspan="3" |R10000
|-
|R12000
|300 MHz
|8MB
| colspan="3" |R12000
|-
|R12000
|350 MHz
|4MB
| colspan="3" |R12000
|-
|R12000
|400 MHz
|8MB
| colspan="3" |R12000
|-
|R14000
|500 MHz
|8MB
| colspan="3" |R12000
|}

==== InfiniteReality ====
The Onyx2 can handle the following revisions of the InfiniteReality:
{| class="wikitable"
|Model
|GE Revision
|Raster Manager
|Display Generator
|Texture RAM (MB)
|Raster RAM (MB)
|-
|InfiniteReality2
|GE14-4
|RM7-16 or RM7-64
|DG5-2 or DG5-8
|16 to 32
|80 to 160
|-
|Reality
|GE14-2
|RM8-16 or RM8-64
|DG5-2 or DG5-8
|16 to 64
|40 to 80
|-
|InfiniteReality2E
|GE16-4
|RM9-64
|DG5-2 or DG5-8
|64 to 128
|80 to 160
|-
|InfiniteReality3
|GE16-4
|RM10-256
|DG5-2 or DG5-8
|256 to 512
|80 to 160
|-
|InfiniteReality4
|GE16-4
|RM11-1024
|DG5-2 or DG5-8
|1,024 to 2048
|2,560 to 5,120
|}
[[File:Onyx2-raion-passionlip.jpg|left|thumb|An Onyx2 owned by Raion with the cube logo. ]]


InfiniteReality2 is how hinv refers to an InfiniteReality that is used in the Onyx2. The InfiniteReality2 however, was still marketed as the InfiniteReality. It is the second implementation of the InfiniteReality architecture, and was introduced in late 1996. It is identical to the InfiniteReality architecturally, but differs mechanically as the Onyx2's Origin 2000-based card cage is different from the Onyx's Challenge-based card cage.

The Reality is a cost-reduced version of the InfiniteReality2 intended to provide similar performance. Instead of using the GE14-4 Geometry Engine board and the RM7-16 or RM7-64 Raster Manager boards, the Reality uses the GE14-2 Geometry Engine board and the RM8-16 or RM8-64 Raster Manager boards. The GE14-2 has two Geometry Engine Processors, instead of four like the other models. The RM8-16 and RM864 has 16 or 64 MB of texture memory respectively and 40 MB of raster memory. The Reality was also limited by the number of Raster Manager boards it could support, one or two. When maximally configured with two RM8-64 Raster Manager boards, the Reality pipeline has 80 MB of raster memory.

The InfiniteReality2E is an upgrade of the InfiniteReality, marketed as the InfiniteReality2, introduced in 1998. It succeeded the InfiniteReality board set and was itself succeeded by the InfiniteReality3 in 2000, but was not discontinued until 10 April 2001.

It improves upon the InfiniteReality by replacing the GE14-4 Geometry Engine board with the GE16-4 Geometry Engine board and the RM7-16 or RM7-64 Raster Manager boards with the RM9-64 Raster Manager board. The new Geometry Engine board operated at 112 MHz, improving geometry and image processing performance. The new Raster Manager board operated at 72 MHz, improving anti-aliased pixel fill performance.

InfiniteReality3 is the next upgrade and one of the most common for the Onyx2 and Onyx3000 on the secondhand market. The only improvement over the previous implementation is replacement of the RM9-64 Raster Manager with the RM10-256 Raster Manager, which has 256 MB of texture memory, four times that of the previous raster manager.

InfiniteReality4 is the ultimate iteration, introduced in 2002. Primarily used on the Onyx3000 and Onyx350 "G-Bricks". The only improvement over the previous implementation is the replacement of the RM10-256 Raster Manager by the RM11-1024 Raster Manager, which has improved performance, 1 GB of texture memory and 2.5 GB of raster memory, four and thirty-two times that of the previous raster manager, respectively.

Below is a performance table offering comparisons:
{| class="wikitable"
|Reality
|5.5
|94 to 188
| colspan="3" |100 to 200
|-
|InfiniteReality2E
|13.1 to 210
|192 to 6,100
| colspan="3" |200 to 6,400
|-
|InfiniteReality3
|13.1 to 210
|5,600
| colspan="3" |6,400
|-
|InfiniteReality4
|13.1 to 210
|10,200
| colspan="3" |6,400
|}
[[File:Onyx2-rear.jpg|thumb|Rear of an Onyx2, minimally configured]]

==== Memory ====
DIMMs are available in sizes of 16, 32, 64 and 256 MB. The memory modules used in the Origin 200 and Origin 2000 / Onyx 2 are of the same type. To support the Origin 2000 distributed shared memory model, the memory modules are proprietary and include directory memory, which contains information on the contents of remote caches for maintaining cache coherency, supporting up to 32 processors. Additional directory memory is required in configurations with more than 32 processors. The additional directory memory is contained on proprietary DIMMs that are inserted into eight DIMM slots set aside for its use.

==== IO6G ====
An IO6G base I/O board is present in every system. It is a XIO card that provides:

* a 10/100BASE-TX Ethernet port
* 2 sets of PS/2 ports
* 4 Serial ports provided by dual UARTs
* 1 internal Fast 20 UltraSCSI single-ended port
* 1 external wide UltraSCSI, singled ended port
* 1 real-time interrupt output for frame sync
* 1 real-time interrupt input (edge triggered)

Also on the card is the Flash PROM, NVRAM and real time clock of the system.

==== PCI ====
The system can utilize PCI with the addition of an Origin 2000 XIO PCI "Shoebox" or individual XTalk PCI adapters inserted in the cage. These are the same sort form factor as Octane units.

=== Operating System Support ===
IRIX Versions from 6.4 to 6.5.30 supported the Onyx2

[[Category:Hardware]]</text>
    <sha1>49031b4c82abbaabb331f549a0383c321924a361</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>File:Altix330.jpg</title>
  <ns>6</ns>
  <id>94</id>
  <revision>
    <id>108</id>
    <timestamp>2025-02-08T04:13:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9" xml:space="preserve">Altix 330</text>
    <sha1>78383a9206a95642428b0a334d04c777efd428a5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Altix 330</title>
  <ns>0</ns>
  <id>95</id>
  <revision>
    <id>109</id>
    <timestamp>2025-02-08T04:13:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Altix330.jpg|thumb|An Altix 330 stock photo]] The SGI Altix 330, is a rack-mounted, entry level server sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and runs RHEL or SLES Linux. The Altix 330 implements the IP5X processor, but follows the IP41 architecture from the earlier Altix 3000 systems.  === Features === Each base module has one PCI slot. Two gigabit ethernet ports, two SAS/Serial ATA drive bays, an external SAS/Seri..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2414" xml:space="preserve">[[File:Altix330.jpg|thumb|An Altix 330 stock photo]]
The SGI Altix 330, is a rack-mounted, entry level server sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and runs RHEL or SLES Linux. The Altix 330 implements the IP5X processor, but follows the IP41 architecture from the earlier Altix 3000 systems.

=== Features ===
Each base module has one PCI slot. Two gigabit ethernet ports, two SAS/Serial ATA drive bays, an external SAS/Serial ATA connector, and an optical drive are included on the system. USB for L1 and NUMALINK were also included.

The different configurations are:

* Base Module
* Compute Expansion Module
* NUMALINK Router
* PA Module

An Altix330 base module supports up to 16GB of RAM.

=== CPU ===
Each Altix 330 BCM will accommodate one or two Itanium 2 processors of the same type. However the 1.3 GHz processors were only offered in a single module, standalone configuration.
{| class="wikitable"
| colspan="2" |CPU Configurations
|-
|CPU Cache
|Speeds (GHz)
|-
|3MB
|1.3
|-
|4MB
|1.4
|-
|6MB
|1.6
|}

=== Memory ===
The Altix 330 supports registered DDR DIMMs with ECC, rated at 266MHz or faster, which are commonly referred to as PC2100, PC2700, etc. Memory throughput was claimed to peak at 10.8 GB/second.

Main memory is organized into two banks of four DIMMs each, or eight slots total, providing up to 16GB of RAM per BCM. DIMMs of 512MB, 1GB, and 2GB are officially supported; it is unclear as of this writing if 4GB parts will work.

=== NUMALink ===
The Altix 330 does not have a console serial port, and does not normally use an external L2 Controller. Instead, when a suitable USB-to-Ethernet adapter is connected to the L1 system controller on a Base Compute Module, that L1 controller becomes a hybrid L1/L2 controller for the system. After configuration the hybrid L1/L2 controller can be used to access the system console, or to control the system using the L3 software installed on a suitable Linux workstation.

Note that the L1 controller on Altix 330 Router Modules may also include the ability to become a virtual L2 controller when supplied with a suitable USB-to-Ethernet adapter.

=== Storage ===
The Altix 330 has an internal bay for two 3.5" drives.

=== Operating System Support ===
The system can run Microsoft Windows up to Server 2008 R2 (Itanium Edition) and GNU/Linux RHEL and SLES up to versions 5 and 9 respectively.</text>
    <sha1>af56ab3c83df25cff3bb57831e4f6a6507525ac4</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>SGI Freeware</title>
  <ns>0</ns>
  <id>96</id>
  <revision>
    <id>112</id>
    <timestamp>2025-02-08T04:18:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "SGI Freeware was an IRIX-compatible distribution of free and open source software built and distributed by SGI employees, and distributed on SGI media."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">SGI Freeware was an IRIX-compatible distribution of free and open source software built and distributed by SGI employees, and distributed on SGI media.</text>
    <sha1>2f4fef56473a68c533286e901a0bfe23bcd9d6da</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>RISC/OS</title>
  <ns>0</ns>
  <id>97</id>
  <revision>
    <id>116</id>
    <timestamp>2025-02-08T04:40:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "RISC/OS was an early UNIX produced by MIPS Computer Systems, and a predecessor of both 4D1 and IRIX. Unlike [[GL2]], RISC/OS was a dual-universe system with both 4.3BSD and System V Release 3 support. It did not support shared libraries."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="237" xml:space="preserve">RISC/OS was an early UNIX produced by MIPS Computer Systems, and a predecessor of both 4D1 and IRIX. Unlike [[GL2]], RISC/OS was a dual-universe system with both 4.3BSD and System V Release 3 support. It did not support shared libraries.</text>
    <sha1>1baf571a2c5d2aa5c942049eba8113d49aa24769</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>68k-based SGIs (IRIS Series)</title>
  <ns>0</ns>
  <id>98</id>
  <revision>
    <id>118</id>
    <timestamp>2025-02-08T04:43:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The earliest SGI systems were 68000-68020 powered graphics terminals and workstations running [[GL2]], a System V UNIX with an unusual for the time focus on graphics. Multibus standard powered machines, they were similar to Sun Multibus systems in many respects."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="262" xml:space="preserve">The earliest SGI systems were 68000-68020 powered graphics terminals and workstations running [[GL2]], a System V UNIX with an unusual for the time focus on graphics. Multibus standard powered machines, they were similar to Sun Multibus systems in many respects.</text>
    <sha1>b249b7c7dc9de4e7fb0e2e2246142ccff6b87741</sha1>
  </revision>
  <revision>
    <id>139</id>
    <parentid>118</parentid>
    <timestamp>2025-02-16T21:07:38Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="282" xml:space="preserve">The earliest SGI systems were 68000-68020 powered graphics terminals and workstations running [[GL2]], a System V UNIX with an unusual for the time focus on graphics. Multibus standard powered machines, they were similar to Sun Multibus systems in many respects.

[[Category:Stubs]]</text>
    <sha1>9a46b800ac7b343f0251a9df7dd83992bdd28156</sha1>
  </revision>
  <revision>
    <id>140</id>
    <parentid>139</parentid>
    <timestamp>2025-02-16T21:09:23Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="327" xml:space="preserve">The earliest SGI systems were 68000-68020 powered graphics terminals and workstations running [[GL2]], a System V UNIX with an unusual for the time focus on graphics. Multibus standard powered machines, they were similar to Sun Multibus systems in many respects.

[[Category:Hardware]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>6b89416b585d27609066db6c4a0f7e83f9f10cb2</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Nekoware</title>
  <ns>0</ns>
  <id>99</id>
  <revision>
    <id>119</id>
    <timestamp>2025-02-10T16:41:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Nekoware is a community project started on Nekochan.net that created and offered MIPS4 packages for IRIX 6.5.21 or higher."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">Nekoware is a community project started on Nekochan.net that created and offered MIPS4 packages for IRIX 6.5.21 or higher.</text>
    <sha1>eb0bf8e9246b7fe647329d1586f885d5b08a4ad2</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Odyssey Pixel Clock Bug Workaround</title>
  <ns>0</ns>
  <id>100</id>
  <revision>
    <id>120</id>
    <timestamp>2025-02-10T17:56:09Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The first-generation Odyssey boards used in the Octane (V6 and V8) have a known pixel clock bug. The bug manifests in 109-193MHz pixel clocks (display frequency, in simple terms, not to be confused with the refresh rate). To work around these limitations, a few methods have been devised:  ==== Simplest: Use a different resolution ==== At risk of stating the obvious, the simplest way is to use a predefined resolution that is not subject to the hardware limitation. An absu..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1039" xml:space="preserve">The first-generation Odyssey boards used in the Octane (V6 and V8) have a known pixel clock bug. The bug manifests in 109-193MHz pixel clocks (display frequency, in simple terms, not to be confused with the refresh rate). To work around these limitations, a few methods have been devised:

==== Simplest: Use a different resolution ====
At risk of stating the obvious, the simplest way is to use a predefined resolution that is not subject to the hardware limitation. An absurdly low resolution will undercut the pixel clock bug. 

==== Easiest Real Solution: Change the refresh rate ====
Using the VFC compiler: http://tech-pubs.net/SGI_misc/vfc_guide_o2.html 

One can make a custom VFC file and put it into &lt;pre&gt;
 /usr/gfx/ucode/ODSY/vof/
&lt;/pre&gt;and then select the appropriate resolution and refresh rate. 

==== More Complicated: Change other parameters ====
There's no tried and true method here, but blanking intervals can be changed as well as other functions. The guide above is among the best in terms of quality and completeness.</text>
    <sha1>96ec737b8bdd4c4a5c11ef9db74f1cfd07dceb4a</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>SGUG RSE</title>
  <ns>0</ns>
  <id>101</id>
  <revision>
    <id>122</id>
    <timestamp>2025-02-10T18:12:11Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "SGUG RSE is a community effort of the Silicon Graphics User Group to develop software for IRIX using a ported version of RPM, along with tdnf and microdnf to provide package management and resolution. It essentially installs itself as a package without any interaction with the larger system.   ==== Toolchain ==== RSE uses GCC 9 which can cross compile with distcc on x86 systems. It uses RPM SPEC files (not to be confused with SGI SPEC files) to generate SRPMs. It is base..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="680" xml:space="preserve">SGUG RSE is a community effort of the Silicon Graphics User Group to develop software for IRIX using a ported version of RPM, along with tdnf and microdnf to provide package management and resolution. It essentially installs itself as a package without any interaction with the larger system. 

==== Toolchain ====
RSE uses GCC 9 which can cross compile with distcc on x86 systems. It uses RPM SPEC files (not to be confused with SGI SPEC files) to generate SRPMs. It is based on Fedora 31. 

==== Packages ====
As of 2025, RSE is still experimental but boasts over 1,000 "packages" of software, of which many are games, media and other software that is of relevance to SGI users.</text>
    <sha1>404680df802e218c09691558d95ebc9b96196190</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>GCC</title>
  <ns>0</ns>
  <id>102</id>
  <revision>
    <id>124</id>
    <timestamp>2025-02-16T04:53:43Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial Commit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5149" xml:space="preserve">The GNU Compiler Collection is officially supported on IRIX through GCC 4.7. Unofficial support by various groups has resulted in versions as high as 9.5 being successfully built. 

=== Officially Supported Versions ===
GCC 3.4.6 is in the Nekoware collection, and is one of the older versions to survive linkrot. GCC 3.3 was distributed via SGI freeware. 4.x versions include 4.6.3 in [https://www.osarchive.org/os/irix/gnu Nekomimiware] (A play on Nekoware's name), and GCC 4.7.1 is packaged by Nekoware as well.  An older version supported GNAT and GNU Java (4.4.x)

=== Unofficial Versions ===
GCC 4.7.4 is cross-compilable as is 8.2 and 9.2 (via SGUG RSE). Raion has made GCC 6.5.0 with C, C++ and Fortran available with fixes applied to improve the compiler. He also released an experimental GCC 9.5.0 in February of 2025. 

=== GCC 6.5.0 Build ===
A minimum compiler version of approximately GCC 4.4.x is required to build GCC 6.5.0 successfully on IRIX, this has not been thoroughly tested. Raion reports using GCC 4.7.4 with fixincludes applied to build IRIX. 

==== Requirements: ====
GCC 4.4.x or later

GMP 6.x

MPC 1.x

MPFR 3.1.x

ISL 0.18 (for Graphite Loop Optimization. 

Binutils 2.23.2 (Link to the  [http://contrib.irixnet.org/raion/gcc-prepatched/binutils-2.23.2.tar.gz prepatched code])

zlib 1.x

libffi version 3.3.1

Bash, any version for compiling GCC 

star or libarchive tar or gnu tar to extract. 

Build zlib and libffi into the prefix for GCC. Make sure they're in the search paths to get picked up. 

Per [http://contrib.irixnet.org/raion/relnotes/neko_gcc6.txt the relnotes], build binutils with the specific commands.

Per the relnotes, prepare the build environment for GCC. Make sure the system ncargs are set appropriately as well. get into bash, set the env up, and run the build and checks. &lt;pre&gt;
### TEST RESULTS
                === gcc Summary ===

# of expected passes            81595
# of unexpected failures        470
# of unexpected successes       15
# of expected failures          171
# of unresolved testcases       17
# of unsupported tests          1806

Failures: https://pastebin.com/eKwMrgUT

                === g++ Summary ===                                                                                                                                                                                                              
                                                                                                                                                                                                                                                 
# of expected passes            93269                                                                                                                                                                                                            
# of unexpected failures        14                                                                                                                                                                                                               
# of expected failures          313                                                                                                                                                                                                              
# of unsupported tests          4151                                                                                                                                                                                                             

Failures: https://pastebin.com/mHunc8bD

                === libstdc++ Summary ===

# of expected passes            9471
# of unexpected failures        119
# of expected failures          66
# of unresolved testcases       2
# of unsupported tests          967

Failures: https://pastebin.com/a0vnnMQi

                === gfortran Summary ===

# of expected passes            42294
# of unexpected failures        124
# of expected failures          78
# of unsupported tests          97

Failures: https://pastebin.com/C30hwj0a

&lt;/pre&gt;

=== GCC 9.5.0 Build ===
A minimum compiler version of approximately GCC 4.6.x is required to build GCC 9.5.0 successfully on IRIX, this has not been thoroughly tested. Raion reports using GCC 6.5.0 with fixincludes applied to build IRIX. 

==== Requirements: ====
GCC 4.4.x or later

GMP 6.x

MPC 1.0.x

MPFR 3.1.x

ISL 0.18 (for Graphite Loop Optimization. 

Binutils 2.23.2 (Link to the [http://contrib.irixnet.org/raion/gcc-prepatched/binutils-2.23.2.tar.gz prepatched code])

zlib 1.x

libffi version 3.3.1

Bash, any version for compiling GCC

star or libarchive tar or gnu tar to extract. 

[https://pastebin.com/T4nc2rhd Raion's 9.5.0 Patch]

Build zlib and libffi into the prefix for GCC. Make sure they're in the search paths to get picked up. 

Per the 6.5.0 relnotes, build binutils with the specific commands.

Make sure the system ncargs are set appropriately as well. get into bash, set the env up, and run the build. Testsuites skipped for time reasons. 

Seemed to work fine on first glance.</text>
    <sha1>9cc1d223214261737191680532747fd64f3642b6</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>IRIS Development Option</title>
  <ns>0</ns>
  <id>103</id>
  <revision>
    <id>125</id>
    <timestamp>2025-02-16T16:26:51Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Initial Commit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="990" xml:space="preserve">IDO, also known by its backend name of uopt, is an IRIX-based compiler used on IRIX versions prior to 6.5 and compiler versions prior to 7.2. However it is unknown when the compiler backend switched from uopt to MIPSPro truly. Estimation is around version 7.3. 

IDO was famously a default compiler for many Nintendo 64 consoles and includes support for the MIPS R4300i CPU and its eccentricities. MIPSPro 7.3 and 7.4 exclude these options. 

==== Known IDO versions ====
IDO has the following known versions:

* IRIS Development Option 4.0
* IRIS Development Option 4.1.x
* Trusted IRIS Development Option 4.0.5
* IRIS Development Option 5.0
* IRIS Development Option 5.1
* IRIS Development Option 5.3
* IRIS Development Option 6.0
* IRIS Development Option 6.1
* IRIS Development Option 7.1
* IRIS Development Option 7.1.1

==== ABI Support ====
Later versions intended for IRIX 6.x include support for n64 ABI and potentially some support for n32 ABIs. All prior versions are purely o32.</text>
    <sha1>5cc1e5e9d437b0eb4eb8f2b722f98d100feb97c8</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Reddit</title>
  <ns>0</ns>
  <id>104</id>
  <revision>
    <id>128</id>
    <timestamp>2025-02-16T17:25:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Reddit has several SGI subreddits.   === List of Subreddits === /r/sgi  /r/irix  /r/silicongraphics"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="99" xml:space="preserve">Reddit has several SGI subreddits. 

=== List of Subreddits ===
/r/sgi

/r/irix

/r/silicongraphics</text>
    <sha1>373bdef003f24826956c2117e21713792006c487</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>SGUG</title>
  <ns>0</ns>
  <id>105</id>
  <revision>
    <id>129</id>
    <timestamp>2025-02-16T17:26:07Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Silicon Graphics User Group is a community for SGI discussion that has a forum and chat system."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="95" xml:space="preserve">Silicon Graphics User Group is a community for SGI discussion that has a forum and chat system.</text>
    <sha1>6fec8e4128413c9305b0aedef829534548c0b167</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Vintage Computer Festival</title>
  <ns>0</ns>
  <id>106</id>
  <revision>
    <id>130</id>
    <timestamp>2025-02-16T17:44:53Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "VCF is a series of festivals and swap meets hosted around the world."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="68" xml:space="preserve">VCF is a series of festivals and swap meets hosted around the world.</text>
    <sha1>d240f97ad4ba90d6531699e3916926831ba4ff28</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>How to Find Commercial Software</title>
  <ns>0</ns>
  <id>107</id>
  <revision>
    <id>131</id>
    <timestamp>2025-02-16T19:11:15Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Software for IRIX can be acquired a number of ways:  === Requesting Software === IRIXNet's policies allow users to request software in the [https://forums.irixnet.org/thread-2258.html Commercial Software Request Megathread] where users can share such things over private messaging.  === Purchasing Software === IRIXNet and SGUG both have forums for selling software. Additionally, eBay and other places are sources for this.   === Dealing with the Licenses === Two forms of l..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="709" xml:space="preserve">Software for IRIX can be acquired a number of ways:

=== Requesting Software ===
IRIXNet's policies allow users to request software in the [https://forums.irixnet.org/thread-2258.html Commercial Software Request Megathread] where users can share such things over private messaging.

=== Purchasing Software ===
IRIXNet and SGUG both have forums for selling software. Additionally, eBay and other places are sources for this. 

=== Dealing with the Licenses ===
Two forms of licensing for IRIX were common: [[Flexlm]] and dongles. Dealing with the former is just a matter of getting a valid license and placing it into the license.dat. Dealing with the latter necessitates using cracks to patch the executable.</text>
    <sha1>5e8aa1222b9a8ad39751ba00f9d4b4d65391853a</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>MediaWiki:Sidebar</title>
  <ns>8</ns>
  <id>108</id>
  <revision>
    <id>133</id>
    <timestamp>2025-02-16T20:37:17Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with " * navigation ** [http://tech-pubs.net Back To TechPubs Home] ** mainpage|mainpage-description ** recentchanges-url|recentchanges * TOOLBOX * LANGUAGES"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">
* navigation
** [http://tech-pubs.net Back To TechPubs Home]
** mainpage|mainpage-description
** recentchanges-url|recentchanges
* TOOLBOX
* LANGUAGES</text>
    <sha1>8fd44cdddd64d9657d177d2421bf98e6d278177b</sha1>
  </revision>
  <revision>
    <id>134</id>
    <parentid>133</parentid>
    <timestamp>2025-02-16T20:38:05Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="151" xml:space="preserve">
* navigation
** http://tech-pubs.net | Back To TechPubs Home
** mainpage|mainpage-description
** recentchanges-url|recentchanges
* TOOLBOX
* LANGUAGES</text>
    <sha1>0396071673751007be999ff09039d21630e7c330</sha1>
  </revision>
  <revision>
    <id>135</id>
    <parentid>134</parentid>
    <timestamp>2025-02-16T20:38:29Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="144" xml:space="preserve">
* navigation
** tech-pubs.net | Back To TechPubs Home
** mainpage|mainpage-description
** recentchanges-url|recentchanges
* TOOLBOX
* LANGUAGES</text>
    <sha1>4aef2b8dd47f2b5ee33d40e5e88a3f8baee3a788</sha1>
  </revision>
  <revision>
    <id>136</id>
    <parentid>135</parentid>
    <timestamp>2025-02-16T20:41:27Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="231" xml:space="preserve">
* navigation
** http://tech-pubs.net | Back To TechPubs Home
** specialpages
** mainpage|mainpage-description
** recentchanges-url|recentchanges
** http://tech-pubs.net/techpubs_sgi.html | SGI TechPubs Mirror
* TOOLBOX
* LANGUAGES</text>
    <sha1>1623d820916b335e1bf0b1c1897dcdcdc0ae1bab</sha1>
  </revision>
  <revision>
    <id>137</id>
    <parentid>136</parentid>
    <timestamp>2025-02-16T20:41:45Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="246" xml:space="preserve">
* navigation
** http://tech-pubs.net | Back To TechPubs Home
** specialpages | specialpages
** mainpage|mainpage-description
** recentchanges-url|recentchanges
** http://tech-pubs.net/techpubs_sgi.html | SGI TechPubs Mirror
* TOOLBOX
* LANGUAGES</text>
    <sha1>a9842c7a50138e58e30db2e4dad734129502dc7e</sha1>
  </revision>
  <revision>
    <id>138</id>
    <parentid>137</parentid>
    <timestamp>2025-02-16T20:42:08Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="254" xml:space="preserve">
* navigation
** http://tech-pubs.net | Back To TechPubs Home
** Special:specialpages | specialpages
** mainpage|mainpage-description
** recentchanges-url|recentchanges
** http://tech-pubs.net/techpubs_sgi.html | SGI TechPubs Mirror
* TOOLBOX
* LANGUAGES</text>
    <sha1>b3ca0c9a5a266bf17a4b9319ec97a3a427fb1e0b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Professional IRIS</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>141</id>
    <parentid>22</parentid>
    <timestamp>2025-02-16T21:09:43Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1956" xml:space="preserve">The first widely produced MIPS powered SGIs, these systems were historically called the IRIS 4D GT series. Commonly called the "Twin Towers" due to the distinctive look caused by the disks being kept in a smaller sidecar tower, these systems are notable for being among the most rare and undocumented MIPS powered SGIs. Released firstly as the 4D/60, then as three models, the high end 4D/80, the midrange 4D/70 and the low end 4D/50 differing by CPU and graphics configuration, and the ultimate 4D/85 released in late 1988. The "Twin Towers" design seems to have carried over into the early POWERSeries systems released much later.
[[File:4D50GT.jpg|thumb]]

=== Hardware ===
The unusual Twin Tower design is the result of engineering decisions that led to the smaller tower containing the disk array of the system, with the larger tower containing the graphics boards. This concept of two asymmetrical towers is distinctive and appears unreplicated by anyone but SGI.

The heart of each system is a MIPS R2000 MIPS I 32-bit RISC CPU, replacing the earlier IRIS 2000 and 3000 model line powered by the Motorola 68000 line. Each system's CPU board could hold a maximum of 16MB RAM, with the 4D/80 allowing an additional set of boards totaling 144MB.

The Clover 1 and 2 systems, called G and GT respectively (for Graphics, and Graphics, Textured presumably) were the primary graphics options of the systems.

Similar to other IRIS4D machines, they used a DB9 custom serial keyboard and mouse, similar to the Personal IRIS.

Some reports point to a 4D/85 Single tower model being offered, but little to nothing is known about it.
[[File:Prime-IRIS.jpg|left|frame]]

=== Operating System Support ===
The Personal IRIS line was available during the "IRIX 3.x" era, but more contemporaneously called 4D1-3.x UNIX era. Support continued into IRIX 4.x and 5.x, and was removed along with all other 32-bit options by 5.3.

[[Category:Hardware]]
[[Category:Stubs]]</text>
    <sha1>534eb781fa081663e49d2638eacbffb38063878a</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Personal IRIS</title>
  <ns>0</ns>
  <id>18</id>
  <revision>
    <id>142</id>
    <parentid>24</parentid>
    <timestamp>2025-02-16T21:10:06Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4787" xml:space="preserve">The Personal Iris was introduced in 1988 as low end workstation to the IRIS 4D series based on MIPS RISC microprocessors. A model name consists of "4D/" and a code designating the CPU and graphics type. The models replaced the "Twin Tower" style Professional IRIS series on the low end market, with the [[Power Series]] taking the higher end market. All Personal IRIS systems use a 32-bit MIPS I core and share some parts commonality with the R3000 Indigo in the 30 and 35 models. The last model (4D/35) was introduced in 1991 and presumably sold through 1993 with the release of the Indy heralding the end of the IRIS line.
[[File:PersonalIris.jpg|thumb|A 4D/35 owned by CB_HK of IRIXNet]]

=== Models ===
The series came in four models differentiated by badging, and the contents of the system module inside the case. No major external differences are otherwise shown. Between the 4D/2x and the 4D/3x systems are major differences. The latter one uses a totally different system board which besides faster processors includes a newly designed memory interface that allows much higher bandwidth and a larger amount of main memory. The system bus of the newer boards is clocked at 30 MHz instead of 10 MHz.
{| class="wikitable"
|Model
|CPU board
|CPU
|Maximum Memory
|-
|4D/20
|IP6
|MIPS R2000 12.5 MHz
|32MB
|-
|4D/25
|IP10
|MIPS R3000 20 MHz
|32MB
|-
|4D/30
|IP14
|MIPS R3000 30 MHz
|128MB
|-
|4D/35
|IP12
|MIPS R3000 36 MHz
|128MB
|}
The 20 and 25 models use industry standard 30-pin SIMMs. The 30 and 35 models use the same RAM modules as the Indigo R3000.

=== Graphics ===
The Personal IRIS had either a Datastation (Server) configuration, or they could utilize VME-based Eclipse or Express graphics, the latter only being usable on the 30 and 35 models due to a common architecture with the [[IRIS Indigo]]

=== Peripherals ===
The Personal IRIS, unlike later SGIs, does NOT possess support for PS/2 and uses the 4D-style DB9 keyboards used by the Personal/Professional IRIS series. To use PS/2 peripherals necessitates an adapter.

Personal IRIS models 4D/20 and 4D/25 have basic audio capabilities onboard. For audio in 4D/30 and 4D/35 an optional board is required that is plugged into a special slot on the mainboard. That additional board is called Magnum Audio Option and offers 16bit/stereo audio instead of the 8bit/mono audio that was offered on the earlier Personal Iris models.

The Personal IRIS has a built in SCSI controller that supports the internal as well as the external SCSI devices. The SCSI connector is located on the back of machine itself (just right of the E-Module) and is also covered by the plastic skin. The internal drives connect to the same SCSI chain that is also available via that external centronics SCSI port. The SCSI controller is narrow SCSI, Western Digital 33C93A.

All Personal IRIS systems allow the owner to install double height 6U VME devices. The VME interface of the Personal Iris also supports busmaster devices which may directly access the main memory of the computer. Only the 4D/30 and 4D/35 models allow VME block transfer due to a new peripheral controller on the system board.

=== Operating System Support ===
The Personal IRIS line was available during the "IRIX 3.x" era, but more contemporaneously called 4D1-3.x UNIX era. Support continued into IRIX 4.x and 5.x, and was removed along with all other 32-bit options by 5.3.

=== Hardware Problems ===

==== Power Supply ====
Power supply problems are not uncommon with these systems. Unplug the power cord, then open the opposite side of the E-Module and remove the sheetmetal. The power supply has 2 replaceable fuses which are worth to check as well as the proper cabling. One fuse is on the small daughtercard, the other is next to that card and usually covered with a blue plastic cap.

==== Onboard Battery ====
Signs of failure: The system fails to boot and returns to PROM after issuing "Can't set tod clock"

This problem has so far been seen only on the later Personal Iris models (4D/30 and 4D/35). The earlier systems may not be affected and just boot with a faulty date/time.

While there also may be other causes, the by far most likely is an empty battery on the CPU board. The original battery is a 3V coin cell made by Duracell (DL2450). The battery is socketed so replacing it doesn't require any soldering. The cost of the battery is approximately 3 USD / 2 EUR.

==== 4MB Memory Modules ====
Signs of failure: System doesn't work when more than one set of 4MB modules is installed.

This is a known problem and a flaw in the systems hardware of 4D/30 and 4D/35 systems which can not be fixed. The bottom line is, that only one 16MB kit (4x4MB) may be installed - there is no limitation regarding 8MB (4x2MB) or 32MB (4x8MB) kits.

[[Category:Stubs]]</text>
    <sha1>d16dbac798221ce6f777ffb73968946882d94769</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>IRIS Indigo</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>143</id>
    <parentid>47</parentid>
    <timestamp>2025-02-16T21:10:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5580" xml:space="preserve">The SGI Indigo (Also known widely as the IRIS Indigo) is a line of high end workstations using the MIPS processor family released as a successor to the Personal IRIS series.

The Indigo R4000 was also the first SGI workstation that that featured the 64bit R4000 RISC CPU on the desktop, the first SGI in general using the new CPU was the Crimson. The Indigo offers builtin audio capabilities and comes in a very well designed and space efficient chassis. With one of the Express graphics options it offers accelerated 3D graphics.
[[File:Indigo2-mag.jpg|thumb|IRIS Indigo owned by CB_HK]]

=== Features ===

* One 32-bit R3000 at 33MHz or a R4000 at 100MHz, or a R4400 at 150MHz.
* A maximum of 96MB RAM on R3000 boards (IP12), and 384MB on R4x00 boards (IP20)
* Two GIO32 slots for expansion boards.
* A Motorola 56000 DSP-driven Audio system.
* Seven different graphics options:

* Entry (LG1/2 board)
* Express (XS8, XS24, XS24Z, XZ, Elan)

=== Peripherals ===
The Indigo, unlike later SGIs, does NOT possess support for PS/2 and uses the same keyboard as the SGI Onyx and Crimson. To use PS/2 peripherals necessitates an adapter.

The graphics board uses the 13w3 connector which requires a SOG compliant monitor.

=== Storage ===
All Indigo systems have three drive bays for internal 3.5" SCSI devices that have to be mounted on special drive sleds to be used in the systems. The upper two of them can be accessed from the outside through a small door which makes them usable for removable media drives. To remove any of the three drives the front plate has to be removed which is impossible if the system is secured with the locking bar.

The skins of the Indigo are colored in a dark blue which has a decent hint of purple to it. On R3000 Indigos the type of the graphics option the machine was shipped with was printed on the front door. On R4000 a small badge was used that in addition to the name of the graphics option included "4000" to denote the faster CPU type.

=== Operating System Support ===
The Indigo when first introduced was based on the R3000 microprocessor. Support for this system was added to 4D1-4.x from beginning on (4D1-4.0). Support for Elan, XZ and XS graphics was added shortly thereafter in 4D1-4.0.2. Next support for the new R4000 based model was added in 4D1-4.0.5E.

General support for the Indigo can be found in the all platform releases of IRIX 5.x. Only the R4000 models were supported by IRIX 6.2 and IRIX 6.5. The support for the remaining legacy systems like the Indigo R4000 was dropped after 6.5.22 making IRIX 6.5.22 the last version to support any of these systems.
[[File:Indigo-front-1000.jpg|thumb|IRIS Indigo from the front]]

=== Hardware Problems ===
The Indigo does have a number of potential failures:

==== Battery Failure ====
Signs of failure: The system fails to boot and repeats the message "Can't set tod clock"

This error is very common these days and it occurs during boot time. It usually means that the onboard battery is empty and that the system can't set it's clock. It is not fatal and some systems even recover when they are run for a while. This error does not occur while the system is running.

The original battery used is a Tadiran TL-5186 3.6V battery. Current replacements are the Sonnenschein SL-340 or SL-840. Both can be installed in the same place as the original battery of the Indigo.

In the long run a cheaper solution is to wire a socket for a generic button cell to the battery connectors on the main board. The socket could be fixed on one of the GIO32 bus placeholders. The Indigo will work just fine with a standard and much cheaper 3 V button cell (like a CR2032).

==== Memory Controller ====
Signs of failure: While booting the system displays a message like "Warning: Revision C Memory Controller (MC) chip needed in order to properly operate with SIMMS of this type."

When upgrading memory on an R4000 Indigo IRIX might issue the above warning if there is no Rev C memory controller installed in the system (This can be checked using /usr/gfx/gfxinfo). If all memory is detected (i.e. shown in hinv) and there are not unusual problems with the system since the upgrade it should be safe to ignore the message. It was added when there were bugs in some memory modules. The upgraded Rev C memory controller contains a workaround for these bugs, but as these have also long been fixed there should be no problems today - even with older MCs.

In later IRIX the warning message has been worded differently: "WARNING: You may need a memory controller revision C because of the type of simms installed. If you don't experience any memory errors you won't need MC revision C"

==== Bad eaddr ====
Signs of failure: The system complains about a bad ethernet address (ff:ff:ff:ff:ff:ff).

In general this means that the EEPROM that contains the hardware ethernet address is dead or contains invalid data. It is an 8 pin MiniDIP serial EEPROM (93C56) which is socketed on the backplane.

In many cases the reason is, that in the Indigo different CPU boards (IP20, then IP12) were used. The location of the address is different between the two boards and is properly relocated when a system is upgraded from IP12 to IP20. When the IP12 is placed back in the system the MAC address is erased.

A possible solution is to place the IP12 in the system and reset the mac address from the PROM monitor using the eaddr command - the IP20 doesn't allow that. After that the system can be used with the IP12 board or upgraded to IP20 which will relocate the address once again.

[[Category:Hardware]]</text>
    <sha1>d459a36b6023684123420ae89a200a294deaa512</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Crimson</title>
  <ns>0</ns>
  <id>42</id>
  <revision>
    <id>144</id>
    <parentid>50</parentid>
    <timestamp>2025-02-16T21:10:50Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5128" xml:space="preserve">The IRIS Crimson or simply Crimson is the successor to the Power Series, first released in 1992. It was the first SGI workstation released with a 64-bit processor.
[[File:IRIS Crimson.jpg|thumb|A typical IRIS Crimson]]
The Crimson was a member of Silicon Graphics' IRIS 4D series of deskside systems; it was also known as the 4D/510 workstation. It was similar to other SGI IRIS 4D deskside workstations, and could utilize a wide range of graphics options (up to RealityEngine). It was also available as a file server with no graphics. 

=== Features ===

* One superpipelined MIPS 100 MHz R4000 or 150 MHz R4400 processor.
* Seven high performance 3D graphics subsystem options deliver performance and features to match any application.
* Up to 256 MB memory and internal disk capacity up to 7.2 GB, expandable to greater than 72 GB using additional enclosures.
* High performance I/O subsystem includes four VME expansion slots, Ethernet and two SCSI channels with disk striping support.
* Seven graphics configurations:

* S, no display, server only
* Entry (LG1/2 board) with VME adaptor*
* Express with VME adaptor*
* ELAN with VME adaptor*
* "Clover2": GTX and GTX(B) boardset
* "Powervision": VGX and VGXT boardset
* "Venice": RealityEngine boardset

&lt;nowiki&gt;*&lt;/nowiki&gt;These boards are identical to the IRIS Indigo

=== Notes ===
The memory modules used in the Crimson are the same as on the MC2 memory board used by the Power Series. However, unlike other IRIS 4D series machines an MC2 board is not recognized by the system. All memory (up to 256MB) must be installed on the IP17 mainboard.

The minimal system configuration consists of two cards: IP17 (CPU mainboard) and IO3B (Input/Output mainboard)

While the MIPS R4000 is a 64-bit processor, the Crimson is only capable of running it in 32-bit mode.

IRIS Crimson can operate with IRIX 6.2, but there are bugs in fx.IP17 in the IRIX 6.2 release. In order to prepare a drive you will either need an earlier version of fx, or you must run fx on another system to partition the drive first.

=== Components ===

==== IP17 ====
The CPU mainboard supports either a 100MHz R4000 or 150MHz R4400 CPU with 1MB L2 memory cache and the memory sub-system.

The bus frequency is half of the core speed, either 50MHz or 75MHz depending on the CPU installed.

The differences between the two versions include the PROM revision and different logic on the board.

The Crimson does not support an MC2 board, any memory up to the maximum amount of 256MB must be installed on the IP17 board.

The Crimson supports only one IP17 board unlike its successor, the rackmount Onyx, which supports multiple CPU boards depending on configuration (the deskside Onyx only supports one CPU mainboard but with multiple processors)

==== I03B ====
The Input/Output mainboard supports the following:

* 2 SCSI channels driven with Western Digital 33C93--one internal device connection and one external device connection
* 2 Centronics connectors on the chassis
* 4 serial ports
* 1 parallel port
* 1 AUI 10Mb ethernet port
* 3 powered peripheral ports (8 Pin DIN)

==== Graphics Subsystems ====
The Crimson could be outfitted with seven different graphics setups depending on the end-user's desired needs. Users seeking a file server could opt for no graphics option, which would mean relying on a terminal or network connection to manage the system as there is no basic graphics capability built into the IP17 or IO3B boards. The six other options consisted of varying levels of performance, ranging from Entry graphics, all the way to RealityEngine. These graphics systems were independent of the IP17 and IO3B boards and could be swapped out in order to provide more or less capability as required.

=== Y2k Bug ===
As the IRIS Crimson had already been replaced by the Onyx and Onyx2 prior to the year 2000, little to no work was done to patch the system prior to the turn of the millennium. While the Crimson is not Y2K proof, the error it encounters is not fatal and can easily be rectified by adding a daemon to startup that will sync the time via NTP and reset the Crimson's internal clock. Failure to re-sync the time will cause the system to gain at least one year each time it is restarted until it reaches the end of the Unix epoch at which time it will cycle back. This has the potential for corrupting files and causing licenses to expire prematurely.
[[File:Crimson-jurassic-classic.jpg|thumb|A "Jurassic Classic" Crimson]]

=== In Popular Culture ===
An IRIS Crimson appeared in the main operations center of Jurassic Park. During one scene in the film, the granddaughter of the park's creator, Lex, used the machine to navigate the filesystem of IRIX 4.0 using the application FSN in order to reactivate the locks on the operations center doors. The increase in popularity of the Crimson following the release of the movie prompted Silicon Graphics to release a special edition model referred to as the "Jurassic Classic." It was notable for being marked as such on the outside of the case, in addition to being signed by Silicon Graphics founder Jim Clark.

[[Category:Hardware]]</text>
    <sha1>6d1386af707492f575e5c1fa3c66969317257e53</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Indy</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>145</id>
    <parentid>52</parentid>
    <timestamp>2025-02-16T21:11:47Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7049" xml:space="preserve">[[File:Indymag.jpg|thumb|500x500px|SGI Indy owned by CB_HK]]
The Indy, code-named "Guinness", is one of the low-end workstations by Silicon Graphics. Selling for around $5000 USD at base price it was one of the cheaper models. It is notable for its common-ness, comparable to the Amiga 500 for Amigas, and its use in development for the Nintendo 64. It was introduced on July 12, 1993 and discontinued on June 30, 1997.

=== Features ===
The Indy is a small desktop (dimensions 41 x 36 x 8 centimetres) computer consisting of a steel frame with a removable bright blue plastic skin. The system is capable of supporting the weight of a small CRT or a modern LCD/LED monitor without damage.

After removing the plastic skin, the power supply, long, thin and bolted to the side of the computer is visible, along with the motherboard, any 3.5" hard disks or the optional Floptical drive, along with the GIO riser and video card, as well as both expansion ports.

==== CPU ====
The processors are supplied on a "Processor Module" board with or without external cache (Primary Cache means no external cache, Secondary Cache means there is an external cache) and range from a 100MHz R4000 to a 180MHz R5000.

Indy's motherboard has a socket for the Processor Module (PM). Early Indys used the 100 MHz MIPS R4000 CPU, which quickly proved inadequate. The Indy, at the bottom of SGI's price list, thus became the primary platform for MIPS's low-cost, low-power-consumption R4600 CPU series. The R4600 had impressive integer performance, but had poor floating-point capability. This, however, wasn't too huge of a problem in a box that was generally not designed for floating-point-intensive applications. For this reason, the R4600 made an appearance outside the Indy line just once, and only briefly, in the Indigo 2. This series of CPU issues, along with the relatively low-powered graphics boards, lower maximum RAM amount, and relative lack of internal expansion ability compared to the Indigo led to the Indy being pejoratively described amongst industry insiders as "An Indigo without the 'go'."

The R4600 chip itself has no L2 cache controller, external controller was used to add 512K of L2 cache. R4600s processor modules both with an L2 cache (SC) and without (PC) are common in the Indy. At the same clock rate, the SC version of the processor module is generally 20 to 40 percent faster than the PC version, due to the memory cache.

The Indy was also the first SGI to utilize the MIPS R5000 CPU, which offered significant advantages over the R4400 and R4600 it replaced. The Indy's 180 MHz R5000 module can be overclocked to 200 MHz by replacing its crystal oscillator chip.

==== Memory ====
The system takes standard 72-pin SIMMS (gold plated SIMMS are recommended to avoid dielectric corrosion) and can take anywhere from as low as 16MB to 256MB, these must be added in sets of 4 at a time since the computer is 64-bits and each SIMM is a 16-bit module.Upon release, the base configuration came at 16MB. IRIX 5.1, the first Operating System for the Indy, did not take full advantage of the hardware due to inadequate memory management and the 16MB configuration failed to even boot. SGI quickly increased the base specification to 32 MB, and shipped free memory upgrades at considerable cost. Subsequent IRIX releases made huge improvements in memory usage.

==== Graphics ====
Graphics are one of three possible types: 8-bit XL, 24-bit XL, and XZ. The 24-bit XL card is the most desirable for collectors due to its decent 2D performance and better than the XZ 3D performance when combined with an R5000 CPU. All three options use the 13W3 connector and require a Sync on Green monitor.

The Indy includes analog and digital video inputs, such as Composite and S-Video, as well as a proprietary digital D-sub used by the Indycam. The system is capable of capturing video at a maximum resolution of either 480i or 576i, depending on region.

It takes a fast machine to capture at either of these resolutions, though; an Indy with slower R4600PC CPU, for example, may require the input resolution to be reduced before storage or processing. However, the Vino hardware is capable of DMAing video fields directly into the framebuffer with minimal CPU overhead.

None of the Indys support video output by default - that would require the Indy Video GIO32 card. In addition, there is an optional video module called CosmoCompress, which offers realtime JPEG video compression and decompression and uses up another GIO32 slot.

==== Networking ====
For networking, the Indy has an on-board AUI, an ISDN port, and a 10Mb Ethernet jack. The AUI and Ethernet cannot be used at the same time, the Ethernet jack takes priority automatically. 10/100Mb cards are available on the used market for faster connection speeds.

==== Storage ====
The Indy has two drive bays for 1-inch tall 3.5" drives. The upper drive bay is externally accessible and may hold a SCSI floptical drive. All external and internal drives share a single Fast SCSI bus (unless a GIO32 SCSI card has been installed). External CD-ROM drive connect via SCSI connector at rear side of the box. Typical drive supports boot, OS install, audio. Special ROM is required to boot from for certain device types.

=== Operating System Support ===
The Indy's basic support came in IRIX 5.1 but that is not a recommended release. The Indy is supported through IRIX 6.5.22, it is recommended to use one of the following releases:

* IRIX 5.3
* IRIX 6.2
* IRIX 6.5.22

IRIX 6.5.22 has the most software available, but will be slow on systems below 128MB. 6.2 and 5.3 are much lighter weight, but have their own limitations.

=== Hardware Problems ===
The component of the Indy most prone to failure is the power supply. Neither the Sony nor the Nidec varieties are more reliable, and both have benefits and drawbacks.

==== MAC/System Serial ====
The Indy's Ethernet address, which doubles as the system's serial number, is stored in battery-backed RAM. This means that when the internal battery dies, so does the system - it will hang at the PROM monitor and refuse to boot any further as a result of the Ethernet address being all FFs. A non-amateur user can replace the PROM battery and reprogramme it. The original battery was made by Dallas Semiconductor, now owned by MAXIM. The original unit was marked the "DS-1386-8K-150", however its replacement unit, the "DS-1386-8K-120" can be directly substituted with no ill effects.

To reset the MAC, it's necessary to use fill commands:

To set the MAC 08:00:69:08:e2:0a, for example, this would be done from the PROM:&lt;pre&gt;
fill -w -v 0x08 0xbfbe04e8

fill -w -v 0x00 0xbfbe04ec

fill -w -v 0x69 0xbfbe04f0

fill -w -v 0x08 0xbfbe04f4

fill -w -v 0xe2 0xbfbe04f8

fill -w -v 0x0a 0xbfbe04fc
&lt;/pre&gt;The MAC address is (usually) on a sticker to the rear of the unit, and hence can be reprogrammed without losing software licenses, which often rely on it to verify ownership. Otherwise, any MAC address in SGI's block is usable.

[[Category:Hardware]]</text>
    <sha1>fe8bbcd13f5034b0e69c22f72e415fe085fafd75</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Indigo2</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>146</id>
    <parentid>55</parentid>
    <timestamp>2025-02-16T21:12:04Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4528" xml:space="preserve">The Indigo 2, codenamed "Fullhouse" is a high end workstation marketed by Silicon Graphics from 1993 to 1997, with production of IMPACT models ending in 1998. The Indigo 2 succeeded the earlier IRIS Indigo line and is the higher end version of the Indy.

=== Features ===
The Indigo 2 is a large teal or purple desktop that is deceptively heavy, around 40lbs. It came with two plastic feet which can be used to set it upright vertically.

==== CPU ====
The Indigo 2 has three distinct variants, each with a specific motherboard and "IP" number or designation:

* IP22 supports an R4000, R4400, or R4600 CPU clocked at 100-250MHz
* IP26 supports the R8000 CPU clocked at 75MHz
* IP28 supports the R10000 CPU clocked at either 175 or 195MHz

IP26 systems were generally referred to as the POWER Indigo 2, while the IP28 systems usually had a grill badge that read "10000."
[[File:Indigo2-purple.jpg|left|thumb|Indigo2 Impact with an R10000]]

==== Memory ====
All three variants had 12 SIMM slots on the motherboard, organized into three banks of four slots each, and took industry standard fast page mode (FPM) 72 pin SIMMs with parity. Speeds should be 60 or 70 nanoseconds, and the internal organization must be 36 bits wide - 8MB x 72 bit parts will not work.

IP22 systems will support up to 384MB with 32MB SIMMs. While the IP26 and IP28 systems both support 64MB SIMMs, published limits for these systems reflected concerns about the amount of heat generated by then-current DRAM chips. According to SGI the R8000-based IP26 systems would only support 640MB (2 banks of 256MB, one of 128MB), while the R10000-based IP28 would support 768MB (3 x 256MB).

Eventually 64MB SIMMs became available that generated less heat, and denser 128MB SIMMs became available. Both the IP26 and IP28 can use these 128MB SIMMs, but with limitations. IP26 systems require some banks to use lower-profile SIMMs to clear the CPU carrier, and SGI described limits on the mix of different density SIMMs in these systems. However owners have reported working configurations of up to 896MB (1 x 128MB, 1 x 256MB, 1 x 512MB bank).

With the IP28 it is possible to achieve a total of 1GB of RAM (2 banks x 512MB, or 2 x 256MB + 1 x 512MB), but unfortunately this appears to be a hard limit based on address logic.

==== Graphics ====
The graphics boards available for the Indigo 2 were the pre-IMPACT Newport and Express boards (which included the SGI XL24, SGI XZ, SGI Elan and SGI Extreme) and the MGRAS IMPACT boards (the SGI Solid IMPACT, the SGI High IMPACT, the SGI High IMPACT AA, and the SGI Maximum IMPACT). IMPACT graphics is not supported by the Power Indigo 2 (R8000 CPU). The Indigo2's replacement, the SGI Octane, offered an upgraded bus but featured the same graphics options, albeit in repackaged form.

The IMPACT units are purple, though it is feasible to upgrade a teal Indigo 2 with proper upgrade parts.An IMPACT-ready Indigo 2 must have an IMPACT-ready riser card, an IMPACT-ready power supply, and a sufficiently recent PROM revision.

==== Networking ====
For networking, the Indigo 2 has an on-board AUI and a 10Mb Ethernet jack. The AUI and Ethernet cannot be used at the same time, the Ethernet jack takes priority automatically. 10/100Mb cards are available on the used market for faster connection speeds. This is near identical to the Indy's configuration.

==== Storage ====
The internal drive bays of the Indigo2 take model-specific carriers. These carriers mate to a backplane using a non-standard connector, and contain devices using a standard 50 pin IDC ribbon cable connector. There may not be enough room in the carrier to use an adapter board to use 68 or 80 pin devices unless using a down-sized device, e.g. a 2.5" hard drive in a 3.5" drive carrier.

=== Operating System Support ===
The first Indigo 2 systems were introduced during the 4D1-4.x era. These were based on the R4000 microprocessor and featured Express graphics (Elan, XZ). Support for new hardware was added in future releases during this period and later on in the 4D1-5.x era.

Major milestones include the introduction of the Impact graphics options as well as the step from the R4000 to the R10000 CPU. For Impact graphics special versions of the IRIX 5.3 and IRIX 6.2 release were offered. Similarly a special release of IRIX 6.2 was made for the R10000 CPU upgrade.

General support for all Indigo 2 variants can be found in the all platform IRIX 6.5. The support for the remaining legacy systems like the Indigo 2

[[Category:Hardware]]</text>
    <sha1>ec7f03d436feeb0931036c1eb7e037695e63870e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Onyx</title>
  <ns>0</ns>
  <id>53</id>
  <revision>
    <id>147</id>
    <parentid>61</parentid>
    <timestamp>2025-02-16T21:12:23Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="45592" xml:space="preserve">[[File:Onyx2 with Multichannel.jpg|thumb|Multichannel Display option for an Onyx]]
The Silicon Graphics Onyx (frequently known as the Onyx1 or Original Onyx, or by its form-factor specific codenames Eveready and Terminator) is a graphics supercomputer introduced by Silicon Graphics in 1993 to replace their short-lived Crimson. Also based on the POWERpath-2 Everest architecture, the Onyx is closely related to the Challenge L/XL systems offered by SGI during the same time period, and shares many parts. In general, the difference between an Onyx and a Challenge L/XL is that while the Challenge usually supports more CPUs and memory (with the exception of the Challenge DM), it does not support the installation of a graphics boardset (with the exception of the Challenge GR). The Onyx sat at the high-end of SGI's early-to-mid 1990s product line, above both the Indigo2 and Indy, and was used for tasks such as visualization, simulation, and early virtual reality systems. The system was succeeded on October 7th, 1996 with the launch of the Onyx2. Though production of new Onyxes ended in March of 1999, with the end of service in December of 2008, SGI continued to use the Onyx brand name on their most capable graphics systems until July of 2003, with the introduction of the Onyx4. 

=== Variants and Naming ===
The Onyx is a highly modular system, and was offered in a number of processor and graphics combinations throughout its lifespan. Though some configurations (such as an R8000-based Onyx with VTX graphics) were not offered officially, most CPU/Graphics combinations were, each under a different name. There were ten different, individually named "major variants" of the Onyx. The table below describes these.
{| class="wikitable"
| colspan="6" |Table of officially-offered Onyx Variants
|-
|Variant Name
| colspan="5" |Meaning
|-
|Onyx RealityEngine2
| colspan="5" |An R4000-based Onyx using a RealityEngine2 graphics subsystem
|-
|Onyx VTX
| colspan="5" |An R4000-based Onyx using a VTX graphics subsystem
|-
|Onyx Extreme
| colspan="5" |An R4000-based Onyx using an Extreme Graphics graphics subsystem
|-
|POWER Onyx RealityEngine2
| colspan="5" |An R8000-based Onyx using a RealityEngine2 graphics subsystem
|-
|POWER Onyx Extreme
| colspan="5" |An R8000-based Onyx using an Extreme Graphics graphics subsystem
|-
|Onyx InfiniteReality
| colspan="5" |An R4000-based Onyx using an InfiniteReality graphics subsystem
|-
|Onyx 10000 RealityEngine2
| colspan="5" |An R10000-based Onyx using a RealityEngine2 graphics subsystem
|-
|Onyx 10000 InfiniteReality
| colspan="5" |An R10000-based Onyx using an InfiniteReality graphics subsystem
|-
|Reality Station
| colspan="5" |An R4000 or R10000-based Onyx using a RealityEngine2 graphics subsystem. Limited to only one CPU
|-
|i-Station
| colspan="5" |An R4000 or R10000-based Onyx using an InfiniteReality graphics subsystem. Limited to only one CPU
|-
| colspan="6" |Note: SGI does not appear to have officially offered a POWER Onyx VTX, an Onyx 10000 VTX, or an Onyx 10000 Extreme.
|}
SGI Workstation/Client Periodic Table November 4th, 1994 demonstrates the naming discrepancy between Onyx and POWER Onyx systems with Extreme Graphics installed. While POWER Onyxes are labeled with a slash as POWER Onyx/Extreme, Onyxes are labeled without the slash.
[[File:Onyx-R10k.jpg|left|thumb|R10000 Onyx variant]]
In some cases, such as on their Periodic Tables, SGI also listed the number of processors after the first portion (the one which represents the CPU) of the name. For example, a system with RealityEngine2 graphics and four R4000 CPUs would be an Onyx/4 RealityEngine2, a system with RealityEngine2 graphics and twelve R8000 CPUs is a POWER Onyx/12 RealityEngine2 and so-on. Interestingly, R4000 systems with Extreme graphics do not use the "slash-CPU" notation, meaning that, for example, an system with two R4000s and a system with four R4000s, each with Extreme Graphics, are both known simply as the Onyx Extreme. The same goes for the R8000-based POWER Onyx, except that the slash is kept with only the number removed. All R8000-based Onyxes using Extreme Graphics are known simply as the POWER Onyx/Extreme. This strange phenomenon can be seen on the November 4th, 1994 Workstation/Client Periodic Table (image on right) and the very similar Workstation/Client Periodic Table rev. 2/14/95 (the only difference of which is a change to the aesthetic of the title and the removal of the Crimson RealityEngine and its replacement with the Reality Station, which is, redundantly, known there as the Reality Station RealityEngine2). While this discrepancy between the POWER Onyx and the regular, R4000 Onyx's naming schemes could be mistaken for a typo, its presence on two similar but different revisions of the Periodic Table makes this unlikely.

=== Architecture ===
[[File:940110-Periodic Table.jpg|thumb|SGI Periodic Table]]
The architecture of the SGI Onyx can be roughly divided into two main parts — the POWERpath-2 bus (frequently known as EBus) and the HIO bus (also known as IBus), including the buses and interfaces which interface with the system via it. While the POWERpath-2 bus provides a high-speed interconnect for CPUs, memory, and the I/O subsystem, the HIO bus provides both direct expansion capabilities using the HIO connectors on the IO4, and interfaces to a number of other system components over FCI (via the F Controller ASICs), VMEbus (via the FCI-connected VMECC), SCSI (via the S1IC) and numerous miscellaneous interfaces (via the EPC).
[[File:Onyx RE2.png|left|thumb|Onyx2 RealityEngine2 diagram]]
POWERpath-2 is the successor to SGI's POWERpath architecture, which they had previously used in their PowerSeries and Crimson systems. While it is officially known as POWERpath-2, it is often called EBus, short for "Everest Bus", Everest being the codename for the system architecture shared by the Onyx and Challenge L/XL. While not the "true" name of the bus, the "EBus" moniker is frequently used both by Onyx owners and by SGI themselves (such as on the slot number label affixed below the slots of the Onyx cardcage). The 256-bit POWERpath-2 bus has a data transfer rate of 1.2GB/s (as compared to the 64MB/s of the original POWERpath), and is used exclusively for the system's core components, the IP19/21/25, MC3, and IO4 boards (not for add-on options or graphics boards). POWERpath-2 is unique to Everest systems (Onyx and Challenge L/XL), and was replaced with the S2MP architecture in the later Onyx2 and Origin2000.
[[File:Onyx Infinite Reality Diagram.png|thumb|InfiniteReality Onyx Diagram]]
While core components are connected to POWERpath-2, their interface with the rest of the system is provided by the IO4 board. The IO4 uses an internal 64-bit bus, which, like POWERpath-2, has two names, those being HIO and IBus. When referring to add-on cards connected to the IO4 using it, it is usually referred to as the HIO (high-speed I/O) bus. However, it is also used internally on the IO4, and it seems that the term "IBus" is preferred here. IBus has a bandwidth of 320MB/s, and is shared by HIO add-ons, VME devices and the graphics subsystem (via F Controller ASICs and the VCAM), and the IO4's built-in EPC I/O controller (which, in turn, creates another bus used for basic I/O devices, the 16-bit PBus) and S1IC SCSI controller. VME devices and graphics boards do not connect directly to IBus. Instead, the IO4 also contains two F Controller ASICs, each of which connects to IBus and creates an FCI, or Flat Cable Interface. These two FCI interfaces are exposed on two connectors towards the rear of the IO4. Attached to these connectors (resting on standoffs above the IO4's PCB, much like the HIO options in front of it) is another board known as the VCAM, or VME Channel Adapter Module. The VCAM serves two primary functions, each using one of the FCI interfaces created on the IO4.

As the name of the device states, one of these functions is to act as an adapter between the system and its VME add-on boards. VMEbus is an industry-standard bus developed by Motorola for systems based on their 68000 processor, and used in many systems both with and without the 68000. Though the Everest family were the final SGI systems to use VMEbus, it was far from the first, with many previous SGI systems and add-ons also using it. The Onyx implements VME Revision C, as well as the A64 and D64 modes of Revision D, allowing VME bandwidth up to 60MB/s when DMA is used. The deskside Onyx has 4 VME slots, one of which is filled by the VCAM, while the rack has either four or twelve slots, depending on cardcage configuration (see below for details). The VCAM provides this VME interface using its onboard VMEBus controller chip, and interfaces the VME bus to one of its FCI interfaces using the VMECC (VME Cache Controller).

The other FCI interface provided to the VCAM is simply passed through to the backplane, for use by the graphics subsystem. This is the other primary function of the VCAM. The graphics subsystem communicates with the host system over its FCI interface using its GFXCC (meaning unknown, but probably "Graphics Cache Controller", in the vein of "VME Cache Controller").

In an Onyx Rack, the number of VME slots available depends on whether the system's third cardcage is used. When only two cardcages are used, the rack Onyx has four VME slots, all in Cardcage 2, one of which is filled by the VCAM attached to the IO4. This is the same configuration found in deskside systems. When the third cardcage is used, eight more VME slots, for a total of twelve, are made available. These slots are divided into two groups, found in slots 1, 2, 3, 4 and 12, 13, 14, 15 in Cardcage 3. Slots 1 and 12, the first of each group, contain a VCAM-like board known as an RVCAM, or Remote VCAM, which provides a VME bus to the three slots next to it. No RVCAMs are required if only two cardcages are used, as the VCAM connected to the system's IO4 is sufficient to control the VME slots in Cardcage 2.

In systems equipped with Extreme Graphics, the VCAM is replaced with a GCAM (meaning unknown, but likely "GIO Channel Adapter Module", in the vein of "VME Channel Adapter Module"), effectively replacing the system's VME bus with a GIO64 bus (albeit in a strange form factor). While the exact components of the GCAM are unknown, it likely uses an ASIC in order to interface the GIO bus to one of the FCI interfaces usually used by the VCAM. Assuming the naming scheme for FCI-connected devices was followed, this chip was likely known as the GIOCC. An adapter is then used to install an Indigo2 Extreme Graphics option in a "VME" (the actual protocol is GIO, but the same physical slots on the backplane are used) slot. While both the GCAM and the adapter are relatively unknown and extremely rare, the adapter is especially hard to find details about. It has been mentioned only a few times on Nekochan Forums, with user "whiter" referring to it as "the GIO2VME adapter" in one post and "AB5 (GIO64 to 9u VME shoehorn)" in another, and user "thegoldbug" referring to it as "a small circuit board (SLAG2) with resistors that connects to the VME bus", going on to conclude that "The GCAM must be doing all the work". In a thread about this board created by whiter, another user, "kshuff", says that he owns an Onyx with Extreme Graphics, and that it was factory-installed in his system. The board appears to have been named the AB5 (possible meaning Adapter Board 5), though the names GIO2VME and SLAG2 are also possibilities, and is seemingly smaller than a usual VME-like board, while consisting of "resistors". Based on this, it is likely a small board, the electronics of which consist solely of passives, located at the rear of a VME slot and containing a GIO64 connector of the sort seen in the Indigo2. In order to mount the non-VME-sized Extreme Graphics boardset in the Onyx cardcage, as well as to affix it to the adapter board, some form of carrier, likely a simple metal frame, was probably used. How the Extreme Graphics boardset's ports were moved to the expansion panels in the cardcage door or the graphics bulkhead below is unknown. It has been noted that a spare GCAM and AB5 board could be used with an Extreme Graphics boardset from an Indigo2 in order to add graphics capabilities to a Challenge L/XL, however thegoldbug, one of the owners of this hardware mentioned above, claims to have attempted this configuration twice, using two different AB5 boards, unsuccessfully. The possibility of adding a non-Extreme GIO64 board such as an IMPACT graphics boardset or other Indigo2 card to an Everest system using the GCAM and AB5 has also been raised, however the conclusion seems to be that it would not be possible due to driver problems.

==== CPU ====
The Onyx's CPUs reside on the IP board, which is installed in a POWERpath-2 slot. Though there are 22 different CPU boards available for the Onyx, they are divided into three main categories by their IP number. While most SGI systems spanning multiple processor families use only one IP number (such as the O2, which is an IP32 system regardless of whether an R10000 or R5000 is installed), the IP number of the Onyx and its CPU board(s) is determined by its CPU family. The IP19 board contains one, two, or four R4400 (R4000-family) processors, and was originally the only processor board offered in Onyx systems. With the introduction of the POWER Onyx and the R8000, the IP21 board, containing either one or two R8000s, was released. Note that because there is no IP21 board with four processors, the usual maximum processor count of 4 in desksides and 24 in racks is halved to 2 and 12, respectively. Finally, with the introduction of the Onyx 10000, the R10000-based IP25 board was introduced, which, like the IP19 board, can contain one, two, or four processors.

Desksides allow one IP CPU board, which must be installed in its designated slot (labeled on the sticker below the cardcage). Given the maximum of four CPUs per board, this means the maximum number of CPUs that can be installed in a deskside system is four. Rack systems are significantly more flexible, having eleven EBus slots, five in Cardcage 1 and six in Cardcage 2. Slot 6 in Cardcage 2 must be filled by the master IO4 board, however the ten remaining slots can be used for either IP CPU boards or MC3 memory boards. Additionally, the five remaining EBus slots in Cardcage 2 (those not filled by the mandatory Master IO4 in Slot 6) may be used for additional IO4 boards, though the five slots in Cardcage 1 cannot. Up to six of these slots may be filled with IP boards, allowing up to 24 CPUs in an Onyx rack system.
{| class="wikitable"
| colspan="7" |Table of Onyx IP CPU Boards
|-
|SGI Part No.
|IP No.
|CPUs
|CPU
|Clock
| colspan="2" |Secondary Cache
|-
| colspan="7" |IP19 (R4000):
|-
|030-0642-xxx
|IP19
|1
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0249-00x
|IP19
|2
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0250-0xx
|IP19
|4
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0525-00x
|IP19
|1
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0374-00x
|IP19
|2
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0375-00x
|IP19
|4
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0720-00x
|IP19
|1
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0652-00x
|IP19
|2
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0653-00x
|IP19
|4
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0806-00x
|IP19
|1
|R4400
|250MHz
| colspan="2" |1MB
|-
|030-0805-00x
|IP19
|2
|R4400
|250MHz
| colspan="2" |4MB
|-
|030-0804-00x
|IP19
|4
|R4400
|250MHz
| colspan="2" |4MB
|-
| colspan="7" |IP21 (R8000):
|-
|030-0636-00x
|IP21
|1
|R8000
|75MHz
| colspan="2" |4MB
|-
|030-0625-00x
|IP21
|2
|R8000
|75MHz
| colspan="2" |4MB
|-
|030-0751-00x
|IP21
|1
|R8000
|90MHz
| colspan="2" |4MB
|-
|030-0702-00x
|IP21
|2
|R8000
|90MHz
| colspan="2" |4MB
|-
| colspan="7" |IP25 (R10000):
|-
|013-1672-00x
|IP25
|1
|R10000
|195MHz
| colspan="2" |1MB
|-
|013-1675-00x
|IP25
|1
|R10000
|195MHz
| colspan="2" |2MB
|-
|030-1107-xxx
|IP25
|2
|R10000
|195MHz
| colspan="2" |1MB or 2MB
|-
|030-1107-xxx
|IP25
|4
|R10000
|195MHz
| colspan="2" |1MB or 2MB
|-
|030-1673-00x
|IP25
|4
|R10000
|195MHz
| colspan="2" |2MB
|-
|030-1673-101
|IP25
|4
|R10000
|195MHz
| colspan="2" |2MB
|-
| colspan="7" |Note: The 030-1673-101 board is unable to load IRIX 6.2, due to its use of CPU Version 3.1. 6.5.x must be used.
|}
The secondary cache of the IP19 board is installed on SIMM modules, though these are not the same ones found in the MC3's slots. These are available in capacities of 256KB and 1MB. The 1MB SIMM is not only four times larger in terms of capacity, but also has a slightly reduced latency.
{| class="wikitable"
| colspan="7" |Table of Onyx IP19 secondary cache SIMMs
|-
|SGI Part No.
|Capacity
|Latency
| colspan="4" |Color Code
|-
|030-0324-00x
|256KB
|10ns
| colspan="4" |Blue Stripe
|-
|030-0660-00x
|1MB
|8ns
| colspan="4" |Yellow Stripe
|}

==== Memory ====
Memory is installed in the Onyx using one or more MC3 boards. A deskside system can take one MC3 board, while a rack can take up to 8. Note that this means that it is impossible for an Onyx rack to have both the maximum CPU configuration and the maximum RAM configuration, as there are simply not enough EBus slots for 8 MC3s and 6 IP boards, let alone any IO4 boards. The MC3 board has 32 slots, each of which can accept a single SIMM of special ECC-protected memory. Three different models of memory SIMM exist, in capacities of 16 and 64 megabytes (with the 64MB version existing in two different variants). The following is a list of MC3 board revisions. It is believed that all revisions should be interchangeable with no effect on compatibility with other parts. However, this has not been exhaustively tested, and as such it is recommended to leave a working system's MC3 board in place when possible, as all MC3 revisions are essentially equivalent in functionality.

List of Onyx MC3 Memory Board Revisions (by SGI Part Number)030-0245-00x

* 030-0604-xxx
* 030-0607-001
* 030-0613-xxx
* 030-0614-xxx
* 030-0614-106

The following is a table of available Onyx memory SIMMs, to be installed on the MC3.
{| class="wikitable"
| colspan="7" |Table of Onyx MC3 Memory SIMMs
|-
|SGI Part No.
|Capacity
|Latency
|Color Code
| colspan="3" |Construction
|-
| colspan="7" |16MB:
|-
|030-0256-00x
|16MB
|60ns
|Pink Stripe
| colspan="3" |Single PCB
|-
| colspan="7" |64MB:
|-
|030-0257-001
|64MB
|60ns
|Purple Stripe
| colspan="3" |Dual-PCB ("Sandwich")
|-
|030-0257-002
|64MB
|60ns
|Purple Stripe
| colspan="3" |Single PCB
|}

==== Graphics ====
Throughout its lifespan, the Onyx was available with four different graphics options. Initially released with a choice of RealityEngine2 or VTX, options for Extreme graphics and InfiniteReality were introduced later.

The performance characteristics of these graphics options are provided in the table below, for easy comparison.
{| class="wikitable"
| colspan="7" |Performance Characteristics and Features of Onyx Graphics Options
|-
|
|RealityEngine2
|VTX
|InfiniteReality
| colspan="3" |Extreme
|-
|Anti-aliased vectors/sec
|2.0M
|1.0M
|7.4M
| colspan="3" |?
|-
|Triangle Meshes/sec
|1.6M
|1.1M
|11M
| colspan="3" |?
|-
|T-Mesh Gouraud Z, lit
|1.0M
|813K
|?
| colspan="3" |?
|-
|T-Mesh Textured
|988K
|600K
|?
| colspan="3" |?
|-
|Quad Strips, Gouraud, Z
|988K
|600K
|?
| colspan="3" |?
|-
|Pixel Fill, smooth, Z
|90M (1x RM )
180M (2x RM)
360M (4x RM)
|90M
|224M (1x RM)
~450M (2x RM)
"&gt;800M" (4x RM)
| colspan="3" |?
|-
|Pixel Fill, Textured, AA
|55M (1x RM)
~115M (2x RM)
230M (4x RM)
|Presumably 55M
|194M (1x RM)
~400M (2x RM)
"&gt;750M" (4x RM)
| colspan="3" |?
|-
|Trilinear Interpolations/sec
|40M (1x RM)
80M (2x RM)
160M (4x RM)
|Presumably 40M
|"&gt;200M" (1x RM)
~400M (2x RM)
"&gt;800M" (4x RM)
| colspan="3" |?
|-
|Convolutions 5x5 separable
|20M
|?
|? (SGI says "TBD")
| colspan="3" |?
|-
|Z-Buffer
|32-bit Integer
|32-bit Integer (?)
|24-bit Floating Point
| colspan="3" |?
|-
|Color
|48-bit RGBA
|48-bit RGB
|48-bit RGBA
| colspan="3" |?
|-
|Color Planes
|192
|192
|192
| colspan="3" |?
|-
|Overlay Planes*
|8
|8
|16
| colspan="3" |?
|-
|Underlay Planes*
|8
|8
|None (?)
| colspan="3" |?
|-
|Max Bits-per-pixel
|256 (1x RM)
512 (2x RM)
1024 (4x RM)
|256
|256 (1x RM)
|512(?) (2x RM)
|1024 (4x RM)
|?
|-
|Texture Memory
|4MB (RM4)
16MB (RM5)
|4MB (RM4)
16MB (RM5)
|16MB (RM6-16)
64MB (RM6-64)
| colspan="3" |?
|-
|Framebuffer Size
|40MB (1x RM)
80MB (2x RM)
160MB (4x RM)
|40MB
|80MB (1x RM)
160MB (2x RM)
320MB (4x RM)
| colspan="3" |?
|-
|Display
|VGA to non-interlaced HDTV (32-bit) or 1600x1200 (48-bit)
|VGA to 1280x1024
|VGA to non-interlaced HDTV
| colspan="3" |?
|-
|32-pixel Read (/sec? meaning unclear.)
|28.3M
|21.1M
|?
| colspan="3" |?
|-
|32-pixel Write (/sec? meaning unclear.)
|29.1M
|26.8M
|?
| colspan="3" |?
|}
Note: Overlay and underlay plane specifications are confusingly worded in sources, and should be taken with

a grain of salt. Meaning of "32-pixel" measurements is unknown, and they are provided verbatim, as listed in

the original source (sgistuff.net). Numbers for dual-RM setups may be interpolated from listed single and quad

specifications, marked with ~ when 4-RM measurement is not precisely 4x the 1-RM measurement. BPP of 512

in dual-RM IR setup interpolated from single being 256 and quad being 1024, however an SGI brochure lists

the dual-RM i-Station as 1024. This is believed to be an error. This brochure also lists some InfiniteReality details

as "greater than" a certain measurement (presumably a conservative estimate). This "&gt;SOMETHING" format is

preserved here. Details for Extreme Graphics are unknown at this time, and should be determined and added.

VTX specs marked "Presumably" are taken from an IR/RE2 comparison with no mention of VTX, and are based

on the single-RM RE2 figure (as VTX is architecturally identical, but has only one RM).

A Note on "RM"

The RealityEngine2, VTX, and InfiniteReality graphics options for the Onyx all utilize a board called the RMx, x being a version. In the case of the RealityEngine2 and VTX, this can be either the RM4 or RM5, whereas InfiniteReality uses one of two variants of the RM6 (RM6-16 or RM6-64). While, in most discussions, this board is referred to simply as the "RM", the meaning of the acronym is less clear than one might imagine. It appears that the majority of Onyx owners, as well as, in many cases, SGI themselves (see their website, circa 1994), refer to the board as the "Raster Manager". However, in the technical papers for both the RealityEngine2 and the InfiniteReality, the authors refer to it as the "Raster Memory" board. Because of this, it appears that, within SGI, there was either disagreement or confusion as to what "RM" stood for. While both would make for the "RM" acronym, it is generally accepted that "Raster Manager" makes more sense (as, while the board does contain memory, it also performs a significant amount of processing, rather than simply storing data).

RealityEngine2

RealityEngine2, often known as "RE2", was, at the time of its release, the highest end graphics option for the Onyx. While it was later repurposed as a lower-end counterpart to the new InfiniteReality, it was originally the most powerful option available. The RealityEngine2 is an improved version of the RealityEngine graphics offered in Crimson and PowerSeries systems, the differentiating factor being the replacement of the eight processor GE8 with the twelve processor GE10. Additionally, the need to terminate Raster Manager boards using a special "terminated" RM4T board (an RM4 with resistors installed in a socket on the board) was removed, with termination now being handled by the system's backplane. The RealityEngine2 consists of three types of board, installed in specialized graphics slots on the backplane.
{| class="wikitable"
| colspan="7" |Table of RealityEngine2 Boards
|-
|SGI Part No.
|Board Name
|Connected to Edge Connector?
|Function
| colspan="3" |Notes
|-
|030-0325-00x
|GE10
|No
|Geometry Engine - Perform geometric graphics calculations
| colspan="3" |N/A
|-
|030-0513-00x
|DG2
|Yes
|Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0359-001 RM4
|Yes
|Raster Manager - Generate image data from geometry
| colspan="4" |40MB framebuffer RAM per RM4, 4MB texture RAM regardless of board count.
|-
|030-0360-001
|RM4T
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |Like RM4, but terminated for pre-Onyx systems. Resistors in jumper block must be removed if installed in Onyx.
|-
|030-0347-00x
|RM5
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |40MB framebuffer RAM per RM5, 16MB texture RAM regardless of board count.
|-
|030-0506-00x
|PAB1
|No
|Paddleboard Interface - Connect RealityEngine2 to Sirius Video board
| colspan="3" |Connects to DG2. Not needed if Sirius Video is not installed.
|}
The GE10 board contains 12 Geometry Engines, at the center of each is an Intel I860XP (not to be confused with the similar but mostly unrelated terms "i386", "x86", "i586", and so-on) RISC processor. While the i860 family of processors never saw use as widespread as hoped, they were found in numerous other niche uses at the time, such as the NeXTcube's NeXTdimension color graphics board, as well as computers from Oki, Stardent, Hauppauge, and Olivetti. It also saw use in Intel's iPSC/860 and Paragon series supercomputers. In the RealityEngine2, these i860XP processors are used to perform geometry calculations for graphics. Each one of these chips has a combined ALU plus floating point performance of 100 megaflops, meaning that, multiplied by the Geometry Engines on the board, each containing one processor, the total compute performance of the GE10 board is 1.2 gigaflops. Each i860XP processor is provided with two megabytes of DRAM. The GE10 also houses the command processor, which is used to control the graphics subsystem and to implement the OpenGL graphics language. The output of these twelve individual geometry engines is transmitted on the Triangle Bus, for use by the RM board. Interestingly, the design of the Triangle Bus on the RealityEngine2's GE10 board is identical to that of said Triangle Bus on the original RealityEngine's GE8 board. While the increased load of the GE10's four extra geometry engines does increase utilization of Triangle Bus bandwidth, the bus was designed to support more than twice the bandwidth required by the original RealityEngine, meaning that in theory, it would work even with 16 Geometry Engines. This meant that the Triangle Bus did not need to upgraded or redesigned during the development of the GE10. The GE10 board does not connect to the edge connector board, and as such installation of a GE10 only requires that the board be inserted into the backplane, like a regular EBus or VME board.

The RM board inputs geometry data from the Triangle Bus, and outputs digital video data to the DG2. The RM board consists of two main types of processor, the Fragment Generator and the Image Engine. Each Raster Manager board consists of five Fragment Generators, with each Fragment Generator driving sixteen Image Engines. While the functionality of the Raster Manager is complex and spans many different tasks (as discussed in the "RealityEngine Graphics" paper, linked below), the basic architecture of the board inputs data from the GE10's triangle bus, before distributing it between five Fragment Generators. The Fragment Generator consists of four ASICs and eight 16 megabit (2 megabyte) DRAM chips, for a total of 16 megabytes per Fragment Generator and 80 megabytes per RM board. The output of the Fragment Generator is then fed into the input of the Image Engine. The RM4 board contains 20 IMP7 Image Engine chips, each of which contains four individual Image Engines. Each one of these IMP7 chips is surrounded by four four megabit (512 kilobyte) DRAM chips, one for each Image Engine inside. The output of these 80 Image Engines is then output to the DG2 board, by way of the edge connector board, which must be installed. The RM4 board provides 40MB of framebuffer memory per board, and adding more RM4 boards can increase this to a total of 160MB (in a four board setup). The RM4 also provides 4MB of texture RAM, though this capacity is not increased by the addition of further RM4 boards. The closely related RM4T is simply an RM4 with some resistors installed in a jumper block towards the rear of the board, for use as a terminated RM4 in a Crimson or PowerSeries system. If installing an RM4T board in an Onyx, these resistors should be removed from the jumper block prior to use, as the Onyx does not require Raster Manager termination. The newer RM5 maintains the same 40MB of framebuffer RAM, but increases texture RAM to 16MB, again not increased when additional boards are installed.

The DG and RM boards must be connected using an edge connector board, installed at the front of the cardcage and connecting all boards below it. The part number of this edge connector is 030-0233-001. This board carries 160 serial, one-bit 50mhz data paths, which together carry the output of the Image Engines to the DG2. In a single-RM system, half of these paths are used, one for each of the 80 Image Engines. In a dual-RM setup, each data path is assigned to a single Image Engine, with all 160 used. In a quad-RM system, these data paths are multiplexed, with each path carrying the output of two Image Engines. This multiplexing is likely the primary reason why a triple-RM system is not possible, as it would require a strange configuration, such as a half-multiplexed, half-direct use of all 160 paths, or some other special-case implementation. With all 160 paths in use, this board provides a bandwidth of 500 megabytes per second.

On the receiving end of the output of the Image Engines is the DG2 board. This board generates the video outputs exposed on the graphics bulkhead's connectors. The data from the Image Engines is first reassembled into what is effectively a digital video signal by ten crossbar ASICs on the DG2, before the image is dithered from 12- to 8-bit color and passed through Digital-to-Analog converters (DACs) for output to the monitor. Like the RM boards, the DG2 board must be connected to the edge connector board. The DG2 board has connectors for the Graphics Bulkhead, which is installed lower in the chassis and connects to it via ribbon cables.

VTX

VTX is a cost-reduced variant of the flagship RealityEngine2 graphics. Architecturally, a VTX subsystem is identical to a RealityEngine2, however it contains half the Geometry Engines and is limited to a single Raster Manager board. While the single RM board and the DG board are identical to those used in a RealityEngine2, VTX replaces the twelve-GE GE10 board with the six-GE GE10V. An SGI Periodic Table from 1993 lists many variants of Onyx in otherwise-identical VTX and RealityEngine2 configurations. This conveniently allows the reader to determine the price of a VTX subsystem relative to a RealityEngine2, as in all cases, systems with VTX graphics cost $40,000 USD less than their RealityEngine2 counterparts. Despite this significant cost saving to the original buyer, it appears that today, at least with regards to systems owned by collectors and those sold on the used market, VTX-powered Onyxes are significantly less common than RealityEngine2 models, perhaps indicating that the lower cost of VTX was not worth the reduced performance to many original buyers. It appears that SGI may have responded to this apparent lack of sales later in the Onyx's life cycle, with late-era Onyx marketing materials usually omitting the option of VTX entirely (though this could also be said to be because of the introduction of the new InfiniteReality graphics subsystem, effectively rendering the once high-end RealityEngine2 the Onyx's budget graphics offering).

InfiniteReality

InfiniteReality is the later of the two flagship graphics options offered for the Onyx. Being the successor to the RealityEngine2, InfiniteReality is the most powerful graphics option available for the Onyx. Like the RealityEngine2 subsystem before it, InfiniteReality consists of three types of board, the GE, DG, and RM. The primary goal of InfiniteReality was to deliver graphics of a quality similar to that of RealityEngine2 at an increased frame rate. A key goal during the development of InfiniteReality's architecture was that it would not only be fully compatible with the Onyx (in addition to the later, higher-bandwidth Onyx2), but that it would be able to utilize most of its performance on both systems. This affected many elements of the boardset's design, from its physical partitioning into GE, RM, and DG boards (so as to fit into the graphics slots in an Onyx), to its use of a display list subsystem with significant architectural changes to that used in the RealityEngine2 (see linked InfiniteReality: A Real-Time Graphics System paper). These architectural changes were necessary to adequately utilize the InfiniteReality in the Onyx, which interfaced with its graphics at a data rate of approximately 200MB/s, in addition to the roughly twice-as-fast Onyx2, which managed 400MB/s.

Like the RealityEngine2, the InfiniteReality uses one GE board, one DG board, and one, two, or four RM boards, connected to the DG via frontplane card-edge connector board. It should be noted that InfiniteReality's RM boards have a greater power consumption than those used in the RealityEngine2, and, as such, only one or two can officially be used in a deskside (while four is limited to a rack). Despite this limitation, it is rumored that, by installing the power boards from a rack system in a deskside, the system could theoretically power four RMs. While it may be possible to provide sufficient power for the additional boards in a deskside, cooling them is still likely to be difficult for the deskside's smaller fans. While a four-RM deskside would certainly be a rare (possibly even unique), powerful, and compact system, those attempting this configuration should exercise extreme caution, understand that they risk severely damaging their system (especially if it seriously overheats), and should understand that this configuration is unsupported and potentially not even possible. Those seeking a reliable, known-good 4-RM InfiniteReality system are advised to look into an Onyx or Onyx2 rack system, where four RMs is an official configuration, and the system already has the necessary cooling and power capacity without any modification.
{| class="wikitable"
| colspan="7" |Table of InfiniteReality Boards
|-
|SGI Part No.
|Board Name
|Connected to Edge Connector?
|Function
| colspan="3" |Notes
|-
|030-0681-003
|GE12-4
|No
|Geometry Engine - Perform geometric graphics calculations
| colspan="3" |"-4" meaningless on Onyx, denotes 4 GEs. Onyx2's GE14 also had a 2 GE "-2" version (in Reality Graphics systems).
|-
|030-0686-004
|DG4-2
|Yes
|Two-channel Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0687-004
|DG4-8
|Yes
|Eight-channel Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0683-004
|RM6-16
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |80MB framebuffer RAM per RM6-16, 16MB texture RAM regardless of board count.
|-
|030-0684-004
|RM6-64
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |80MB framebuffer RAM per RM6-64, 64MB texture RAM regardless of board count.
|-
|030-0506-00x
|PAB2
|No
|Paddleboard Interface - Connect InfiniteReality to Sirius Video board
| colspan="3" |Connects to DG4-2 or DG4-8. Not needed if Sirius Video is not installed.
|}
Like in the RealityEngine2, data moving through the InfiniteReality begins on the GE board. It is accessed from the host system using the Host Interface Processor, which then provides it to the Geometry Distributor. The Geometry Distributor handles distribution of geometry processing workload among the GE board's four Geometry Engines. The Geometry Distributor is capable of distributing data using either a round-robin or least-busy distribution scheme, though least-busy has a slight performance advantage. The Geometry Distributor provides data to the Geometry Engines in the form of commands, each of which contains an identifier assigned by the Geometry Distributor. The Geometry-Raster FIFO buffer later uses these identifiers to reconstruct the order of the commands before they were sent to the Geometry Engines.

Unlike RealityEngine2's twelve Intel i860 XP processors, InfiniteReality uses four custom in-house ASICs. The Geometry Engine chips used by InfiniteReality each contain three cores, meaning that, like it's predecessor's 12 i860 XPs, the InfiniteReality could be said to have twelve processors for geometry (three in each of the four ASICs). However, this analogy should be used with caution. While the RealityEngine2 truly did have 12 Geometry Engines, each three-core InfinteReality ASIC contains only one 2560-word (32-bit words) on-chip memory, shared by all three of its cores. As such, even ignoring the fact that they are no longer on separate chips, the cores that make up an InfiniteReality Geometry Engine are not as independent with regards to memory as the Geometry Engines are on the RealityEngine2 (where each i860 XP has access to 2MB of its own, off-chip DRAM). This single memory for all three cores also allows them to easily share data, if necessary.

At the output of the four Geometry Engines lies the Geometry-Raster FIFO, an SDRAM-based FIFO buffer capable of storing up to 65536 vertices. As stated above, this FIFO is also responsible for properly ordering its data, based on the identifiers assigned by Geometry Distributor.

The data then moves from the GE board to the RM boards, via the Vertex Bus. While the purpose of the Vertex Bus (to carry data between the GE and RM boards) is similar to that of the RealityEngine2's Triangle Bus, it is implemented differently (see paper linked below), resulting in a significant performance improvement. Data sent over the Vertex Bus is broadcast to all Fragment Generators. The InfiniteReality RM board contains a single Fragment Generator and 80 Image Engines. The Fragment Generator is, as was also the case with its predecessor, composed of multiple chips (the SC Scan Converter, TA Texel Address Calculator, eight TM Texture Memory controllers, and four TF Texture Filtering ASICs). Like on the RealityEngine2, data from the GE board is first processed by the Fragment Generator, then by the Image Engines. Because there is only one per RM board, an InfiniteReality RM board's single Fragment Generator uses all 80 of the image engines on the board, unlike on the RealityEngine2, where each of the five Fragment Generators is given 16 of the 80 total Image Engines. The InfiniteReality also continues the trend of combining four individual Image Engines onto a single Image Engine chip, meaning that only 20 Image Engine chips are needed.

Two variants of the Onyx InfiniteReality RM board are available. The RM6-16 has 16MB of Texture RAM (TRAM), while the RM6-64 has 64MB. Each RM board maintains one copy of texture RAM, meaning that, while the amount of physical texture memory in a system increases when additional RM boards are installed, the amount of usable texture memory remains the same, as the memory on the newly-installed RM board(s) is used simply duplicate the data on the existing RM(s). Because each board must retain its own copy of texture RAM, RM6-16 and RM6-64 boards cannot be mixed in a single system (as, having only a quarter the texture memory, an RM6-16 would be unable to store a full copy of the texture memory contents of an RM6-64). Both the RM6-16 and RM6-64 have 80MB of framebuffer RAM per RM board, double the 40MB seen on the RealityEngine2. Unlike TRAM, framebuffer RAM is not duplicated between RM boards, meaning that more RM boards will increase the total amount of framebuffer RAM in the graphics subsystem, up to a maximum of 320MB (with four RM boards).

Like on the RealityEngine2, the output of the RM boards is sent to the DG board via an edge connector board mounted at the front of the cardcage. The edge connector spans the four RMs, connecting to each, and also connects to the DG board, but does not connect to the GE board or any other boards in the cardcage. This edge connector carries 160 serial data paths, the same configuration used in the RealityEngine2, however their use is more flexible on InfiniteReality systems. The RealityEngine2 utilizes one path per Image Engine in one-RM and two-RM configurations, and multiplexes the outputs of each pair of Image Engines onto a single path in a four-RM configuration. This means that, while the video bandwidth of the frontplane is fully utilized in two-RM and four-RM setups, where all 160 paths are driven by at least one Image Engine, single-RM systems utilize only half of the bandwidth, leaving the other 80 paths unused. Though an InfinteReality system also has only 160 paths for its potential 320 Image Engines, it uses them more efficiently in single-RM configurations. While two RMs will assign one path to each of the 160 Image Engines, and four RMs will multiplex the output of 320 Image Engines onto 160 paths, single-RM InfiniteReality systems allow each of the 80 Image Engines to drive two of the 160 data paths on the frontplane, doubling per-Image-Engine bandwidth. Since InfiniteReality systems use all 160 data paths in all configurations, the bandwidth of the InfiniteReality frontplane is a fixed 1200MB/s.

These 160 signals are recieved by four ASICs at the input of the Display Generator board (these ASICs also add the cursor on top of the incoming video). The video is then sent to one of the Display Generator's two or eight (see below) channels. A DG channel is able to resize its video in realtime (e.g. for output as NTSC/PAL video), and can also control the timing of its output. This timing control is the purpose of the Genlock and Swap Ready BNC connectors on the graphics bulkhead, and is discussed in greater depth in the "InfiniteReality: A Real-Time Graphics System" paper linked below. The channel's 12-bit-per-component digital video signal is then passed through 8-bit DACs, which generate the final analog video signal. It should be noted that Channel 1 contains additional hardware, not found on other channels, allowing it to also output composite and S-Video signals.

InfiniteReality's DG4 board is available in two variants. The DG4-2 has two channels, and was the lower-end "standard" option, while the higher-end DG4-8 has eight channels. It should be noted that the DG4-2 PCB has footprints for the components required to provide extra six channels, however, these components are unpopulated. Particularly noticeable are the footprints for the six large BGA chips along the edge of the board, as well as the six QFPs beside them. Towards the middle of the board is a connector for the PAB2 Sirius Video paddleboard, which must be installed if the InfiniteReality boardset is being used alongside a Sirius Video board. The DG4 board has connectors for the Graphics Bulkhead, which is installed lower in the chassis and connects to it via ribbon cables.

Extreme Graphics

Extreme Graphics is the lowest-end graphics option available for the Onyx. It was also available in the Indigo2, where it was the highest-end option until the introduction of IMPACT graphics in 1995. While Extreme Graphics boardsets are relatively common in Indigo2s, they are a rare and largely undocumented option in the Onyx. While it is generally understood that the graphics boardset itself is identical to the one found in an Indigo2, the hardware used to connect it to the Onyx (which does not normally have GIO64 slots) is poorly documented. Further information about the adapters required for this configuration can be found in the "Architecture" section above. The graphics hardware itself is simply a regular Extreme Graphics boardset (see Indigo2). This configuration is rare, and this, combined with the fact that it is rarely mentioned in official SGI documents, is likely the reason for the scarcity of information surrounding it.

==== I/O ====
The IO4 I/O Controller implements the basic I/O functions for Onyx systems:

* Ethernet Controller
* two fast/wide 16 bit SCSI-2 controllers
* four serial ports (3x RS232, 1x RS422)
* a parallel port
* two Flat Cable Interfaces (for VME or Graphics)

In Onyx Deskside systems 1 IO4 controller can be installed, in rackmount Onyxes up to 6 of these boards can be installed.

=== Operating System Support ===
It is recommended to run IRIX 6.5.22 on all revisions/versions of this machine.

=== Troubleshooting ===
No power-on

If a previously working Onyx with no known power supply issues suddenly refuses to power on (specifically no DC GOOD light, no front panel controller functioning) it is possible the Dallas chip located on the System Controller Board (rear access panel of the Onyx) has gone bad. Replacing the Dallas DS12887 with a new production version will allow the system to power on correctly.

=== Links ===

* "RealityEngine Graphics" paper: &lt;nowiki&gt;http://www.sgistuff.net/hardware/graphics/documents/K.Akeley-RealityEngine.pdf&lt;/nowiki&gt;
* "InfiniteReality: A Real-Time Graphics System" paper: &lt;nowiki&gt;http://people.csail.mit.edu/ericchan/bib/pdf/p293-montrym.pdf&lt;/nowiki&gt;

[[Category:Hardware]]</text>
    <sha1>d7bbdd9ba67a2a71eac56e641db438910993effc</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Origin 2000</title>
  <ns>0</ns>
  <id>58</id>
  <revision>
    <id>149</id>
    <parentid>101</parentid>
    <timestamp>2025-02-16T21:12:50Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3380" xml:space="preserve">For the graphics deskside variant, see the [[Onyx2]] article
[[File:Origin 2000 Deskside .jpg|thumb|Front view of an Origin 2000 Deskside]]
The SGI Origin 2000, code name ''Lego'', is the successor of the SGI Challenge line. Sold in deskside, rack and multi-rack configurations, the Origin 2000 is a highly modular and scalable system.
[[File:Deskside Oriigin 2000 Profile.jpg|left|thumb|Another view of an Origin 2000 Deskside in profile]]

=== Features ===
Each Origin 2000 module is based on nodes that are plugged into a midplane. Each module can contain up to four node boards, two router boards and twelve XIO options. The modules are then mounted inside a deskside enclosure or a rack. Deskside enclosures can only contain one module, while racks can contain two. In configurations with more than two modules, multiple racks are used.

The following table shows a list of models and their possible configurations:
{| class="wikitable"
|Model
|CPUs
|Memory
|I/O
|Chassis
|-
|Origin 2100
|2 to 8
|Up to 16 GB
|12 XIO
|Deskside
|-
|Origin 2200
|2 to 8
|Up to 16 GB
|12 XIO
|Deskside
|-
|Origin 2400
|8 to 32
|Up to 64 GB
|96 XIO
|1-4 Racks
|-
|Origin 2800
|32 to 128
|Up to 256 GB (512 GB unsupported)
|384 XIO
|1 to 9 racks (with Meta Router)
|}
A 3-slot PCI cage can be installed as well as a maximum of 10 XIO cards, giving a massive amount of expandability. This is in addition to 5 hard disks and one 5.25 option drive.

==== CPU ====
[[File:Onyx2 rack.jpg|thumb|An Origin 2000 rack unit is seen here with an onyx2 graphics unit]]
The following table shows the possible CPU configurations.
{| class="wikitable"
|Processor
|Clockspeed
| colspan="3" |Cache
|-
|R10000
|180 MHz
|1MB
| colspan="2" |R10000
|-
|R10000
|195 MHz
|4MB
| colspan="2" |R10000
|-
|R10000
|250 MHz
|4MB
| colspan="2" |R10000
|-
|R12000
|300 MHz
|8MB
| colspan="2" |R12000
|-
|R12000
|350 MHz
|4MB
| colspan="2" |R12000
|-
|R12000
|400 MHz
|8MB
| colspan="2" |R12000
|-
|R14000
|500 MHz
|8MB
| colspan="2" |R12000
|}

=== Memory ===
DIMMs are available in sizes of 16, 32, 64 and 256 MB. The memory modules used in the Origin 200 and Origin 2000 / Onyx 2 are of the same type. To support the Origin 2000 distributed shared memory model, the memory modules are proprietary and include directory memory, which contains information on the contents of remote caches for maintaining cache coherency, supporting up to 32 processors. Additional directory memory is required in configurations with more than 32 processors. The additional directory memory is contained on proprietary DIMMs that are inserted into eight DIMM slots set aside for its use.

==== IO6 ====
An IO6 base I/O board is present in every system. It is a XIO card that provides:

* a 10/100BASE-TX Ethernet port
* 2 Serial ports provided by dual UARTs
* 1 internal Fast 20 UltraSCSI single-ended port
* 1 external wide UltraSCSI, singled ended port
* 1 real-time interrupt output for frame sync
* 1 real-time interrupt input (edge triggered)

Also on the card is the Flash PROM, NVRAM and real time clock of the system.

==== PCI ====
The system can utilize PCI with the addition of an Origin 2000 XIO PCI "Shoebox" or individual XTalk PCI adapters inserted in the cage. These are the same sort form factor as Octane units.

=== Operating System Support ===
IRIX Versions from 6.4 to 6.5.30 supports the Origin 2000.

[[Category:Hardware]]</text>
    <sha1>410099d31e6edf74c2ed352bd6ba20d1a767a239</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Octane</title>
  <ns>0</ns>
  <id>70</id>
  <revision>
    <id>150</id>
    <parentid>78</parentid>
    <timestamp>2025-02-16T21:13:05Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9250" xml:space="preserve">[[File:An Octane2 setup.jpg|thumb|An Octane2 setup]]
The Octane and its later version, the '''Octane2''', code named Speed Racer, is a high end workstation marketed by Silicon Graphics between 1996 and 2004. It is an SMP-capable (dual CPU) machine running the MIPS R10000 to R14000 series of processors. The main differences between the Octane2 and the Octane are configuration-related. The Octane 2 has upgraded motherboard, power supply, front plane and graphics options, but it's entirely possible to retrofit these upgrades to a regular Octane, creating the "Octane 1.5" as many have popularly dubbed it. 

=== Features ===
[[File:Octane-new-logo.jpg|left|thumb|An Octane late model with the "sgi" logo]]
The Octane's system-board is designated as IP30. The system is based on SGI's Xtalk (Pronounced Cross-talk) architecture. This means it does not use a system bus; instead it has a router XBOW (Pronounced cross-bow) that connects any two of its ports. One of the ports is used for the processor and memory subsystem, one is available for PCI (actually PCI-64) expansion and four are XIO slots (packet-based high-bandwidth bus, somewhat similar to HyperTransport). This makes it very similar to a single node of the SGI Origin 200 system.

The XIO is here and there bridged to PCI-64, using a chip named BRIDGE. The places where it happens include the system board (for the IOC3 multi-I/O chip, two ISP1040B SCSI controllers and RAD1 audio), MENET cards (four IOC3s) and the PCI cage (used for PCI cards in Octane). ARCS is provided as the boot firmware, similar to all contemporary SGI computer systems.

==== CPU ====
The Octane series has single and dual CPU modules. A second CPU cannot be added to a single CPU module, therefore upgrading to two requires replacing the entire CPU module.

What follows is a table of all known models:
{| class="wikitable"
|Processor
|Cache
|Single (Mhz)
|Dual (Mhz)
|-
|R10000SC
|1MB
|175, 195, 225, 250
|175, 195, 225, 250
|-
|R12000SC
|2MB
|270, 300, 400
|270, 300, 400
|-
|R12000SCA
|2MB
|360, 400
|360, 400
|-
|R14000SCA
|2MB
|550, 600
|550, 600
|}

==== Memory ====
The Octane allows 256 MB to 8 GB of system memory, using proprietary 200-pin DIMMs. There are two system board revisions. The first revision (part number 030-0887-00x, usually distinguished by a black handle) only supports 2GB of RAM while the later one (part number 030-1467-001, with a silver handle) supports up to 8GB. The -0887 revision of the mainboard will work with all 32-128 MB DIMMS and the stacked variant of 256MB DIMMS, but not the later single-board version (SGI P/N 9010036). The memory subsystem has vast reserves of bandwidth that can be directly served by the Xbow router to any XIO card.

The Octane's memory controller is aptly named HEART. It acts as a controller between the processor, the memory (SDRAM) and the XIO bus.

==== Graphics ====
Graphics on the Octane are provided by a series of cards: SI, SI+T, SSI, MXI. These are updated XIO versions of Solid Impact (SI), High Impact (SI+T) and Maximum Impact (MXI) from the SGI Indigo2 that were internally designated by SGI as 'MARDIGRAS'. The boards were accelerated and reengineered with faster geometry engine and texture modules to create their new versions: SE, SE+T, SSE, MXE. The SI/SE provides 13.5MB of framebuffer memory while the SSE and MXE have a 27MB framebuffer. The '+T' indicates an additional high speed RDRAM texture board which gives 4MB of texture memory, which is practically indispensable, though quite expensive and fragile. The SI/SE+T has one texture board while the MXI/MXE has 2 texture boards, however, the 2 boards in the MXI/MXE do not double the available texture memory to the system. It just doubles the texture performance.

Later Octanes and Octane 2s support the SGI VPro graphics board series, designated 'ODYSSEY'. The first VPro series cards were the V6 and V8. The main differentiator being that the V6 has 32MB of RAM (unlike the MARDI GRAS option, framebuffer memory and texture memory come from the same pool) and V8 having 128MB. Later, the V10 (32MB) and V12 (128MB) were introduced. The main difference with the new VPro V10/V12 series is that they had double the geometry performance of the older V6/V8. V6 and V10 can have up to 8MB RAM allocated to textures (2X more than the textured-enabled MARDIGRAS options), while V8 and V12 can have up to 108MB RAM used for textures.

The VPro graphics subsystem consists of an SGI proprietary chip set and associated software. The chip set consists of the buzz ASIC, pixel blaster and jammer (PB&amp;J) ASIC, and associated SDRAM.

The buzz ASIC is a single-chip graphics pipeline. It operates at 251 MHz and contains on-chip SRAM. The buzz ASIC has three interfaces:

* Host (16-bit, 400-MHz peer-to-peer XIO link)
* SDRAM (The SDRAM is 32 MB (V6 or V10) or 128 MB (V8 or V12); the memory bus operates at half the speed of the buzz ASIC.)

* PB&amp;J ASIC

As with the MARDIGRAS boards, all VPro boards support OpenGL in hardware (MARDIGRAS is OpenGL 1.1 + SGI Extensions, while VPro upgraded support to OpenGL 1.2) and OpenGL ARB imaging extensions, allowing for hardware acceleration of numerous imaging operations at real-time rates.

Compatibility: The V6/V8 boards require an XBOW 1.3 board, but the V10/V12 boards do appear to require an XBow 1.4 frontplane.

==== I/O and HEART ====
The Octane supports Ultra Wide SCSI devices and has two SCSI controllers. System can have up to three internal 3.5" SCSI SCA devices. Octanes use special mounting sleds for the hard drives which are compatible with Origin 2000, Origin 200 and Onyx2. The system also has external Ultra Wide SCSI bus.

The aptly named HEART is the core of the Octane. It integrates a SDRAM memory controller, a XIO device, an interrupt controller and a processor bus interface for up to four R10000-class processors.

The HEART can be accessed in two ways from the processor. The first one is through the PIU (Programmed I/O Unit) at 0xFF0000 in processor physical address space. The other one is at widget 8 in XIO address space. The only one way available to other XIO devices is through the widget interface, so the Interrupt Status Set register is mapped there at address 0x80.

The HEART contains a SDRAM memory controller with ECC. ECC errors are signaled to the CPUs by interrupts.

The XIO bridge is one of the main functions of the HEART. There are three access windows defined for each XIO widget number. There is a window at 0x10000000+ W*0x1000000 for widget number W, a window at 0x800000000+W*0x80000000 and a window at 0x1000000000+W*0x1000000000.

Note that XIO accesses are deeply pipelined by default. Due to that fact, writing to any XIO widget may not have any effect for several hundred cycles. To guarantee finalization of all posted writes it is required to read the widget flush register.

The XIO bridge in HEART provides also some Flow Control features for two channels. They allow to schedule a hiwater IRQ for any given XIO register address. If the register is an input to a FIFO, as is the case with the IMPACT graphics board, exceeding a prescribed number of writes to this register would cause a FIFO hiwater condition. As you already know, the XIO writes are posted and not immediately executed. Catching the hiwater condition in the HEART and not in the card allows to trap it in a more reliable way.

The HEART interrupt controller is visible from the PIU as a set of registers: interrupt mask registers for all processors (IMR0:3), an interrupt status register (ISR) and ISR clear and set registers that allow atomic manipulation of the ISR.

The XIO side consists of a single register 0x80 that can accept either an atomic ISR bit set command or an atomic ISR bit clear command. These commands cause asserting and deasserting IP7:2 bits in the CPUs whose IMRs contain the bit in question.

A small part of the HEART is a programmable interval timer, consisting of 24-bit COUNT and COMPARE registers. The IRQ can be delivered only to the IP6 bit, which is the highest-priority CPU interrupt except internal CPU timer and HEART error IRQs. The timer counts at 12.5 MHz, every 8th internal HEART cycle (1/4th of the XIO frequency).
[[File:Octane2.jpg|thumb|Another view of an Octane2]]
The HEART controls also the Number In a Can associated with processor modules. It features a standard SGI issue MicroLAN controller. 

=== Octane 2 Upgrades ===
Octane 2 has a revised power supply, system-board and XBOW. Octane 2 also shipped with VPro graphics and supports all available VPro cards (V6, V8, V10 and V12). Later revision Octanes also included some of the improvements mentioned.

The case is blue instead of the green used by the original, the plastics are compatible between the two and the chassis is identical.

=== Operating System Support ===
The Octane was first supported by IRIX version 6.4 with IMPACT or "Mardi Gras" graphics (SI/SSI/MXI and later Enhanced versions). Support for VPro or "Odyssey" graphics in Octanes was introduced with IRIX 6.5.10 for V6/V8, and in IRIX 6.5.11 for V10/V12. (Drivers were released to support V10/V12 under 6.5.10.) All versions of IRIX through 6.5.30 include support for the Octane family machines.

[[Category:Hardware]]</text>
    <sha1>6675f9d989b73a498a169a786cf95395b77b7833</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>O2</title>
  <ns>0</ns>
  <id>74</id>
  <revision>
    <id>151</id>
    <parentid>82</parentid>
    <timestamp>2025-02-16T21:13:20Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9498" xml:space="preserve">The Silicon Graphics O2, codename Moosehead, is an entry-level Unix workstation introduced in 1996 by Silicon Graphics, Inc. (SGI) to replace their earlier Indy. Like the Indy, the O2 uses a single MIPS microprocessor and was intended to be used mainly for multimedia. Its larger counterpart was the SGI Octane. The O2 was SGI's last attempt at a low-end workstation.

=== Features ===
O2 features a proprietary high-bandwidth Unified Memory Architecture (UMA) that connects the various system components. The O2 is a highly-integrated system, with CPU, graphics accelerator, memory, SCSI controller, and I/O all incorporated into a single system module, which can be slid out of the chassis with the flip of a lever. A PCI bus is bridged onto the UMA with one expansion slot available. The O2 has a designer case and a modular design, with space for two Ultra SCSI drives mounted on special sleds (only one in the later R10000/R12000 models) and an optional video capture / sound module mounted on the far left side. Further information on the design and construction of the O2 can be found in SGI service manuals on Techpubs. Detailed breakdown pictures and an IRIX hinv dump can be found here.

An O2's unique system ID (MAC address) is stored on the small PCI riser card that connects the PCI card holder to the motherboard. If this riser card is swapped, the corresponding black plastic badge on the rear of the case should be swapped as well to preserve consistency.

WARNING: The O2 system module should NEVER be removed or installed while the power cord is connected. Doing so can permanently damage the motherboard.

==== CPU ====
The O2 comes in two distinct CPU flavours; the low-end MIPS 180 to 350 MHz R5000- or RM7000-based units and the higher-end 150 to 400 MHz R10000- or R12000-based units. The 200 MHz R5000 CPUs with 1 MB L2-cache are generally noticeably faster than the 180 MHz R5000s with only 512 KB cache. There is a hobbyist project that has successfully retrofitted a 600 MHz RM7xxx MIPS processor into the O2.

There is also a hobbyist project that has successfully retrofitted a 600 MHz R7000 MIPS processor into the O2. In theory faster CPUs at 900MHz any beyond are possible, but this would require the public release of the O2 PROM source code which at present is not available and probably never will be.
[[File:O2 full setup.jpg|thumb|An O2 in full setup]]
A recall of some early versions of the RM7000A 350Mhz CPU is thought to have hastened the removal of the O2 from SGI's product line.

==== Memory ====
There are eight DIMM slots on the motherboard and memory on all O2s is expandable to 1 GB using proprietary 239-pin SDRAM DIMMs. The Memory &amp; Rendering Engine (MRE) ASIC contains the memory controller. Memory is accessed via a 133 MHz 144-bit bus, of which 128 bits are for data and the remaining for error-correcting code (ECC). This bus is interfaced by a set of buffers to the 66 MHz 256-bit memory system.

Original SGI-branded O2 DIMMs are either single-sided (SS) with memory chips on only one side of the module or double-sided (DS), and are color-coded to assist in identification. 3rd party DIMMs may or may not follow these conventions. Knowing the current memory configuration is important as DIMMs must be installed according to a number of specific rules.

* The DIMMs in slots 1 and 2 make up Bank A. DIMMs in slots 3 and 4 make up Bank B, and so on.
* A bank of two slots must have a DIMM in each slot or be empty (except for slots 1 and 2, Bank A, which must always be populated.)
* The two DIMMs in any bank must be of the same size and type.
* The largest size DIMMs must be in Bank A.
* DIMM banks must be filled sequentially, beginning with bank A.
* Equal or smaller size DIMMs must be in Bank B, and so on.
* Do not skip banks, or the memory will not be recognized.

To install high density (128 MB) DIMMs, PROM revision 4.4 or higher is required. With older PROM revisions maximum memory is 256 MB. For IRIX 6.3 there are patches to upgrade the PROM as described in "Silicon Graphics® O2® Workstation Memory Installation Instructions", for IRIX 6.5 PROM images come with the operating system and overlays CD sets.

==== Graphics ====
[[File:SGI O2.jpg|left|thumb|An early-model O2 with the original cube logo]]
The CRM chipset that SGI developed for the O2 shares OpenGL calculations with the CPU. Due to the unified memory architecture, video memory is shared with main memory, and there is effectively an 'unlimited' amount of texture memory. Another useful feature is that any incoming video data from the Audio/Video option can be mapped directly as an OpenGL texture without having to perform a copy or move.

ICE (Image Compression Engine — a dedicated 64-bit R4000-based processor containing a 128-bit SIMD unit running at 66 MHz, which is used to accelerate various image and video operations)

The O2 Video system supports two simultaneous input video streams and one output video stream which can be separated into two outputs, one carrying pixel information, the other carrying alpha (key) information.

Using the O2 Video system, it is possible to capture live video into the computer's memory which can then be displayed in a graphics window on the screen or further processed by an application. It is also possible to generate video output from images in memory, which can be displayed on a standard video monitor, or recorded to a VTR. Using the VL programming library, a program can capture video in either the RGB or YCrCb color spaces, and either full or reduced size formats, and in a format usable for input to the compressor/decompressor, display on the graphics screen, or as an input to a graphics processing and/or texture operation.

SGI offered two video options for the O2/O2+: the AV1 interface and the AV2 interface.

The AV1 interface supports Composite and S-Video (Y/C) (both analog), and Digital I/O via the Camera/Digital Video port. The analog I/O jacks are for use with standard analog video equipment, supporting both PAL and NTSC video formats. There are a variety of controls available that allow the user or programmer to set various parameters used for the decoding and encoding of the video signals. The digital input of the AV1 is for use with the O2Cam Digital System Camera, or can be connected to an optional digital video input and output adapter to interface to standard SMPTE259M serial digital video devices.

The AV2 interface supports two ITU-601 (CCIR-601) serial digital video input connectors and two similar output connectors, as well as GPI input and output and analog (black burst) sync input and loop through.

==== I/O ====
I/O functionality is provided by the IO Engine ASIC. The ASIC provides a 33-bit PCI-X bus, an ISA bus, two PS/2 ports for keyboard and mouse, and a 10/100 Base-T Ethernet port. The PCI-X bus has one slot, but the ISA bus was present solely for attaching a Super I/O chip to provide serial and parallel ports.

=== O2+ ===
[[File:SGI O2+ by Mattst88.jpg|thumb|An O2+, property of mattst88]]
The O2+ is a special variant of the SGI O2 with a purple/grey color scheme, top of the line multimedia, CPU and memory. It was produced in very low quantities and has remained a valuable item for collectors, selling for many times the going rate for O2s on average.

=== Operating System Support ===
IRIX versions 6.3 and 6.5 (up to the latest overlay - 6.5.30) are supported on this machine, however, only in 32-bit mode, due to the nature of the O2's internal architecture. For CPU-specific versions, see also: IRIX for O2.

Besides the default CD-based Installation, the O2 also supports network installation.

=== Hardware Problems ===
The Toshiba CD-ROM drives in the O2 commonly throw a small white plastic gear from the tray motor. Symptoms include the tray either refusing to open or refusing to stay closed. This problem is relatively easy to fix by opening the CD-ROM drive and pushing the gear back onto the motor shaft, then adding a small amount of glue to keep the gear in place. To avoid damaging the tray mechanism during ordinary use, do not push it closed: use the "inject" command instead.

To quote kjaer in a Nekochan forum post &lt;nowiki&gt;https://web.archive.org/web/20170821000034/http://forums.nekochan.net/viewtopic.php?f=3&amp;t=16726667&lt;/nowiki&gt; "...there is a pressfit nylon pinion on the transport motor that opens and closes the drive tray, and also raises and lowers the optical pickup assembly (moves it closer to the disc after the tray closes, and moves it away from the disk before the tray opens). This pinion splits when it ages, and when this happens the static friction between pinion and spindle is no longer sufficient to hold the torque required to lift the optical pickup. The drive interprets this as a mis-load and ejects the tray." A further discussion with images can be found &lt;nowiki&gt;https://web.archive.org/web/20170820231441/http://forums.nekochan.net/viewtopic.php?f=3&amp;t=16727779#p7360973&lt;/nowiki&gt;

==== Memory ====
The O2's proprietary memory modules are highly susceptible to dirt and shock, particularly during shipping. The symptoms of a bad memory contact include random memory errors and a total inability to boot, with a solid red or blinking amber LED at startup. Careful cleaning and re-seating of memory will typically solve such problems, though the DIMMs should also be carefully inspected for missing surface-mount components, which can be easily knocked-off via mishandling.

[[Category:Hardware]]</text>
    <sha1>769a64b994c268a178cafbab6ea420228aa8f021</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-08 04:06:18+00|103">
  <title>Origin 3000</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>152</id>
    <parentid>87</parentid>
    <timestamp>2025-02-16T21:13:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6498" xml:space="preserve">[[File:Origin 3000 Rack Cluster.jpg|thumb|An Origin 3000 Rack cluster]]
The SGI Origin 3000, is the successor of the SGI Origin 2000 line. Unlike previous versions, it did not offer a deskside version, opting for full and half rack configurations instead. It also introduced the "brick" architecture used by many Chimera architecture SGIs.

=== Features ===
Physically, the Origin 3000 is based on "bricks" - rackmounted modules that provide a specific function, that are connected together using NUMAlink 3 cables for modules providing compute functions, or Crosstown2 cables for modules providing I/O functions. These bricks are mounted in a standard 19-inch rack. There are two racks for the Origin 3000, a 17U-high half rack, and a 39U-high tall rack. Architecturally, the Origin 3000 is based on the distributed shared memory NUMAflex architecture. The NUMAlink 3 system interconnect uses a fat tree hypercube network topology.

The following table shows a list of models and their possible configurations:
{| class="wikitable"
|Model
|CPUs
|Memory
|Chassis
|-
|Origin 3200
|2 to 8
|Up to 16 GB
|Half Rack
|-
|Origin 3400
|4 to 32
|Up to 16 GB
|1 Full Rack
|-
|Origin 3800
|16 to 512
|Up to 1 TB
|1-16 Full Racks
|-
|Origin 3900
|4 to 512
|Up to 1 TB
|1 to 4 Full Racks
|}

==== C-Brick ====
[[File:Comparison of the O2k to the O3k.jpg|left|thumb|Comparison of the Origin 2000 and Origin 3000, side-by-side]]
The C-Brick (Compute Brick) is a 3U-high enclosure that contains CPUs on a PCB. The node contains two or four processors, the local and directory memory, and the Bedrock ASIC. The two processors and their secondary caches is contained on a PIMM (Processor Integrated Memory Module) daughter card that plugs into two 240-pin connectors on the node board. Initially, the Origin 3000 used the 360 MHz R12000 and the 400 MHz R12000A processors with 4 or 8 MB of secondary cache. In May 2001, the 500 MHz R14000 was introduced with 8 MB of secondary cache and in February 2002, the 600 MHz R14000A was made available. Near the end of its lifetime, the C-Brick was updated with 800 MHz MIPS processors.

==== CX-Brick ====
[[File:Origin 3000 Full Rack.jpg|thumb|An Origin 3000 Rack]]
The CX-Brick is a 4U-high enclosure that is only used in Origin 3900 and Onyx 3900 systems. It differs from the C-Brick by containing four node boards and eight-port router ASIC. The CX-Brick can support up to 16 processors and 32 GB of memory. The CX-Brick initially used the IP53 motherboard that supported 500 MHz R14000 and 600 MHz R14000A processors with 8 MB secondary caches, later upgraded to use the R16000 and R16000A. It connects to the system using NUMAlink 3.

=== R-Brick ===
The R-Brick (Router Brick) is a 2U-high enclosure that features an eight-port router ASIC. Its purpose is to route NUMAlink packets throughout the system to connect the C-Bricks together. R-bricks for the Origin 3400 have a router ASIC with two ports disabled to prevent them from being upgraded into Origin 3800 systems.

=== I-Brick ===
The I-Brick is a 4U-high enclosure that provides boot I/O functions for the Origin 3000. It features five hot swappable PCI-X slots, with three clocked at 33 MHz and two at 66 MHz on two separate buses, two sled-mounted 3.5-inch Fibre Channel hard drives and a proprietary CD-ROM drive. The I-Brick also provides a 10/100BASE-T Ethernet port, an IEEE-1394 port, a serial port, two USB ports as well as a real time clock and NVRAM for storing configuration information through the IO9. It connects to the system using Crosstown2.

==== IX-Brick ====
The IX-Brick is a 4U-high enclosure that is only used in Origin 3900 and Onyx 3900 systems. It an updated version of the I-brick with 133 MHz PCI-X expansion slots. It connects to the system using Crosstown2 cables.

=== V-Brick ===
The V-brick is a 4U-high enclosure that supports two InfinitePerformance (Commercial name for VPro/Odyssey Graphics) graphics pipes. Each graphics pipe consists of a 128 MB SGI VPro V12 graphics card. The V-brick connects to the system using Crosstown2 cables. This was one of two options for graphics.

=== G-Brick ===
The G-brick is a 18U-high enclosure that supports the InfiniteReality graphics subsystem. Each G-brick can support two InfiniteReality3 or InfiniteReality4 graphics pipes, although only one pipe can have four raster manager boards while the other can have two. The G-brick connects to the system using Crosstown2 cables.

==== Other Bricks ====
[[File:G-Brick.jpg|thumb|An Origin 3000 G-brick]]
Some systems were offered with D, P, PX and X Bricks. D is for data, and contains Fibre Channel, P and PX are PCI-X peripheral bricks, and X is an XIO brick.

=== Memory ===
The C-Brick supports 512 MB to 8 GB of local memory through eight DIMM slots organised into eight banks by using proprietary 100 MHz ECC DDR SDRAM DIMMs with capacities of 256 MB, 512 MB and 1 GB. The data path between the DIMM and the Bedrock ASIC is 144 bits wide, with 128 bits for data and 16 bits for ECC. Because the Origin 3000 uses a distributed shared memory model, directory memory is used to maintain cache coherency between the processors. Unlike the Origin 2000, which requires dedicated proprietary DIMMs for the directory memory, the Origin 3000's directory memory is integrated in the same DIMMs that contain the local memory. Due to this, there are two kinds of DIMM used in the Origin 3000: standard DIMMs, which supports systems with up to 128 processors, and premium DIMMs, which supports systems with more than 128 processors. The 256 MB DIMM is a standard DIMM, the 1 GB DIMM is a premium DIMM and the 512 MB DIMM can be either.

=== Power Supply ===
The Origin 3000 uses a "Power Bay" that contains up to 6 hot swappable powersupplies and provides the Bricks of the system with power (48VDC). It is connected to a wall outlet using a Power Distribution Unit. For this reason, most configurations require 240V. The 3400 and 3800 configurations had alternative setups for power.

=== L2 and L3 Controllers ===
The L2 and L3 Controllers are control systems used to manage the status of each brick in the system and to issue commands, monitor the environment and more. The L2 controller is a small Linux-based silver box that runs Linux on an embedded PowerPC system. The L3 controller was a Linux-based console that could manage several L2 systems.

=== Operating System Support ===
IRIX Versions from 6.5.15 to 6.5.30 supports the Origin 3000.

[[Category:Hardware]]
[[Category:Stubs]]</text>
    <sha1>aacd70012c25e5baf1a6f625a728eef22107007b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Origin 300</title>
  <ns>0</ns>
  <id>62</id>
  <revision>
    <id>153</id>
    <parentid>70</parentid>
    <timestamp>2025-02-16T21:13:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5165" xml:space="preserve">[[File:O300.gif|thumb|Origin 300 rack unit]]
The SGI Origin 300 is a rack-mounted, mid range server sold by Silicon Graphics from 2001 to 2004. The 300 was offered in two to 32 processor configurations, at speeds ranging from 400 to 600MHz over the lifetime of the model. The Origin 300 is not a member of the later Chimera family, though it shares superficial and functional similarities with it. Its closest relative is the SGI Fuel. 

=== Features ===
Each CPU brick has two PCI slots across a PCI bus. All compute bricks are equipped with an IO8 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, and a twisted pair Ethernet connection.

=== CPU ===
Each brick can take dual or quad CPU configurations. The CPUs are attached to the main board, thus a configuration upgrade requires removal of the entire main board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|2MB
|500
|500
|-
|4MB
|600
|600
|}

=== Memory ===
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Fuel, Origin/Onyx350. and the Tezro. There are a total of eight slots, organized into two banks of two slots. This results in a memory capacity from 512 MB to 4 GB total system memory.

All DIMMS for the Origin 300 use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory, which remains unused in the Fuel. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

=== I/O ===
The IO8 card provides SCSI backplane support, and a 100Mbit Ethernet port. Two PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Origin 300 leverages NUMALink heavily to link bricks together. Each unit has a NUMALink and an XIO port, used to link various subsystems together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to eight CPU "bricks" (2 rackmount units high each) with up to four CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink3 cables going to a central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Origin 300 has a front bay for two U160 SCSI drives. It uses proprietary sleds for this purpose.

These sleds are standard off-the-shelf parts used by a number of high-volume server manufacturers, but were apparently only used by SGI on the Origin and Onyx 300 models.

Often Origin 300 systems will be split up and the individual bricks sold to different buyers. While many of these bricks never had hard drives installed, SGI did install sleds with baffles to maintain airflow. This is good news for buyers, as the plastic baffles can be removed and hard drives installed in their place.

The units typically have a sticker on the front of the sled showing the identifier "Assy A06447-00x" where the "-00x" may end in any digit. The second line of the label includes what may be an additional part number ("203368", as seen in the thumbnail image to the right) and a manufacturing code of some kind. It is unclear whether the manufacturing code indicates time of production, plant, batch run, or something else entirely.

However the assembly number from SGI units has not always been useful when searching for replacement parts in the Internet. It was suggested that Intel part number 746797-001 may be the same OEM part.

The 746797-001 part number is referenced in some sources as being used on Intel's SR1200/2200 and ISP2150G servers (black bezel). However images from some eBay auctions appear more similar to the Origin 350-style drive sled, and indeed the Intel product guide for the SR1200 has diagrams showing a unit more similar to that used in the Origin 350.

=== Onyx 300 ===
An Onyx 300 is an Origin 300 NUMALinked to a G-Brick.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator.

=== Operating System Support ===
The Origin 300 was supported beginning with IRIX 6.5.14, and is supported through IRIX 6.5.30

[[Category:Hardware]]</text>
    <sha1>f5cb0be023f1f951bb048454cb424369f86d66ec</sha1>
  </revision>
  <revision>
    <id>186</id>
    <parentid>153</parentid>
    <timestamp>2025-02-16T21:36:07Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5165" xml:space="preserve">[[File:O300.gif|thumb|Origin 300 rack unit]]
The SGI Origin 300 is a rack-mounted, mid range server sold by Silicon Graphics from 2001 to 2004. The 300 was offered in two to 32 processor configurations, at speeds ranging from 400 to 600MHz over the lifetime of the model. The Origin 300 is not a member of the later Chimera family, though it shares superficial and functional similarities with it. Its closest relative is the [[Fuel]]. 

=== Features ===
Each CPU brick has two PCI slots across a PCI bus. All compute bricks are equipped with an IO8 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, and a twisted pair Ethernet connection.

=== CPU ===
Each brick can take dual or quad CPU configurations. The CPUs are attached to the main board, thus a configuration upgrade requires removal of the entire main board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|2MB
|500
|500
|-
|4MB
|600
|600
|}

=== Memory ===
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Fuel, Origin/Onyx350. and the Tezro. There are a total of eight slots, organized into two banks of two slots. This results in a memory capacity from 512 MB to 4 GB total system memory.

All DIMMS for the Origin 300 use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory, which remains unused in the Fuel. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

=== I/O ===
The IO8 card provides SCSI backplane support, and a 100Mbit Ethernet port. Two PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Origin 300 leverages NUMALink heavily to link bricks together. Each unit has a NUMALink and an XIO port, used to link various subsystems together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to eight CPU "bricks" (2 rackmount units high each) with up to four CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink3 cables going to a central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Origin 300 has a front bay for two U160 SCSI drives. It uses proprietary sleds for this purpose.

These sleds are standard off-the-shelf parts used by a number of high-volume server manufacturers, but were apparently only used by SGI on the Origin and Onyx 300 models.

Often Origin 300 systems will be split up and the individual bricks sold to different buyers. While many of these bricks never had hard drives installed, SGI did install sleds with baffles to maintain airflow. This is good news for buyers, as the plastic baffles can be removed and hard drives installed in their place.

The units typically have a sticker on the front of the sled showing the identifier "Assy A06447-00x" where the "-00x" may end in any digit. The second line of the label includes what may be an additional part number ("203368", as seen in the thumbnail image to the right) and a manufacturing code of some kind. It is unclear whether the manufacturing code indicates time of production, plant, batch run, or something else entirely.

However the assembly number from SGI units has not always been useful when searching for replacement parts in the Internet. It was suggested that Intel part number 746797-001 may be the same OEM part.

The 746797-001 part number is referenced in some sources as being used on Intel's SR1200/2200 and ISP2150G servers (black bezel). However images from some eBay auctions appear more similar to the Origin 350-style drive sled, and indeed the Intel product guide for the SR1200 has diagrams showing a unit more similar to that used in the Origin 350.

=== Onyx 300 ===
An Onyx 300 is an Origin 300 NUMALinked to a G-Brick.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator.

=== Operating System Support ===
The Origin 300 was supported beginning with IRIX 6.5.14, and is supported through IRIX 6.5.30

[[Category:Hardware]]</text>
    <sha1>a5781f077c2723378b6685334bb80f21d31c5820</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Origin 350</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>154</id>
    <parentid>68</parentid>
    <timestamp>2025-02-16T21:14:15Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6530" xml:space="preserve">[[File:Origin350 .jpg|thumb|400x400px|Origin 350 Server]]
The SGI Origin 350, and its graphics-equipped sibling the '''Onyx350''', is a rack-mounted, mid range server sold by Silicon Graphics from 2003 to 2007. This system uses MIPS-based processors and offers a number of advances over the Origin 300 model that preceded it. The 350 was offered in two to 32 processor configurations, at speeds ranging from 600 to 1,000MHz over the lifetime of the model. The Origin 350 is a member of the Chimera family (IP53), which includes Origin 350, Onyx 350, and the Tezro Rackmount. All three systems have the same basic hardware - the Origin 350 (Chimera Server) with a VPro card becomes the Onyx 350 (ChiBlade), and the ChiBlade can be configured into a Chimera Rackmount Workstation (Tezro Rack) using the L1's make rmws 1 command. The Chimera Rackmount Workstation cannot accept remote serial numbers, and therefore cannot be connected via NUMALink.

=== Features ===
Each CPU brick has four PCI slots across two PCI busses. Each CPU brick also has a Fuel-style XIO slot, which can accept a DMediaPro DM3 card or a VPro graphics card. The first CPU brick in a system has a single PCI slot holding an IO9 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, audio I/O and a twisted pair Ethernet connection. Other kinds of bricks are available that are dedicated to disk storage or further PCI slots.

The different configurations are:

* Base Compute Module - Includes an IO9, a SCA SCSI backplane (for disks), appropriate cables for disk backplane + IDE CDROM and a daughtercard that provides PS/2 keyboard/mouse and four additional serial ports
* Expansion Compute Modules - These may or may not include the IO9+backplane, but lacks the daughtercard/keyboard/mouse/extra serial ports
* Memory and PCI Expansion (MPX) Modules - Lacks the IO9+backplane and daughtercard/keyboard/mouse/extra serial ports.
* 2UPX Module - PCI Only Expansion Module; a standard 2U Origin 350 chassis with four PCI-X and one XIO-2 slot without processor, memory or Bedrock ASIC. Because the 2UPX does not have a BedRock ASIC, it uses the external XIO port when linked to Origin 350 Compute Modules.

An Origin 350 cannot be booted by itself without the presence of an IO9 card, it requires the IO9 to start up. If a brick lacks it, one must be installed or otherwise the brick must be numalinked.

=== CPU ===
Each brick can take dual or quad CPU configurations the same as the Tezro. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|4MB
|600,700,800
|600,700,800
|-
|8MB
|700,800
|700,800
|-
|16MB
|1000MHz
|1000MHz
|}

=== Memory ===
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Fuel, and the Tezro. There are a total of eight slots, organized into four banks of two slots. This results in a memory capacity from 512 MB to 8 GB total system memory.

All DIMMS for the Origin 350 use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

=== I/O ===
The IO9 card provides SCSI backplane support, 3.5mm Audio, and a 1Gbit Ethernet port. Three PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Origin 350 leverages NUMALink heavily to link bricks together. Each unit has a NUMALink and an XIO port, used to link various subsystems together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to eight CPU "bricks" (2 rackmount units high each) with up to four CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink3 cables going to a central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Origin 350 has a front bay for two U160 SCSI drives. It uses proprietary sleds for this purpose.

The Origin/Onyx 350, Prism, Altix 350, and Altix 450/4x00 all use the same drive carriers. These are standard parts used by a number of manufacturers, notably Intel's SC5200, SRSH4, SR1300/2300, and SR1400/2400 and Sun's v60x and v65x servers.

The units carry "Assy A65278-00x" on a sticker, where the "-00x" may end in any digit though "-005" seems common. This assembly number can be useful when searching for parts in the Internet. According to SR1300/SR2300 support documents at intel.com, the Intel accessory part number for the drive carrier is FXX2DRVCARBLK, UPC code "7 35858 14621 0" and "MM #" 835853. However note that there is some indication that Intel may recycle these accessory part numbers in the FXX- form between different models.

=== Onyx 350 ===
An Onyx 350 is an Origin 350 with a V10/V12 graphics card attached to the XIO2 slot inside, or an Origin 350 attached to a G-Brick.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator called an L3 controller.

It is recommended to use 1GHz boards in the Origin 350, not a Tezro desktop, for the reason of airflow and longevity.

=== Operating System Support ===
The Origin 350 was supported beginning with IRIX 6.5.15, and is supported through IRIX 6.5.30

[[Category:Hardware]]</text>
    <sha1>0ea629e890de6c0f6604becb7a33c5796393bc69</sha1>
  </revision>
  <revision>
    <id>187</id>
    <parentid>154</parentid>
    <timestamp>2025-02-16T21:36:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6534" xml:space="preserve">[[File:Origin350 .jpg|thumb|400x400px|Origin 350 Server]]
The SGI Origin 350, and its graphics-equipped sibling the '''Onyx350''', is a rack-mounted, mid range server sold by Silicon Graphics from 2003 to 2007. This system uses MIPS-based processors and offers a number of advances over the [[Origin 300]] model that preceded it. The 350 was offered in two to 32 processor configurations, at speeds ranging from 600 to 1,000MHz over the lifetime of the model. The Origin 350 is a member of the Chimera family (IP53), which includes Origin 350, Onyx 350, and the Tezro Rackmount. All three systems have the same basic hardware - the Origin 350 (Chimera Server) with a VPro card becomes the Onyx 350 (ChiBlade), and the ChiBlade can be configured into a Chimera Rackmount Workstation (Tezro Rack) using the L1's make rmws 1 command. The Chimera Rackmount Workstation cannot accept remote serial numbers, and therefore cannot be connected via NUMALink.

=== Features ===
Each CPU brick has four PCI slots across two PCI busses. Each CPU brick also has a Fuel-style XIO slot, which can accept a DMediaPro DM3 card or a VPro graphics card. The first CPU brick in a system has a single PCI slot holding an IO9 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, audio I/O and a twisted pair Ethernet connection. Other kinds of bricks are available that are dedicated to disk storage or further PCI slots.

The different configurations are:

* Base Compute Module - Includes an IO9, a SCA SCSI backplane (for disks), appropriate cables for disk backplane + IDE CDROM and a daughtercard that provides PS/2 keyboard/mouse and four additional serial ports
* Expansion Compute Modules - These may or may not include the IO9+backplane, but lacks the daughtercard/keyboard/mouse/extra serial ports
* Memory and PCI Expansion (MPX) Modules - Lacks the IO9+backplane and daughtercard/keyboard/mouse/extra serial ports.
* 2UPX Module - PCI Only Expansion Module; a standard 2U Origin 350 chassis with four PCI-X and one XIO-2 slot without processor, memory or Bedrock ASIC. Because the 2UPX does not have a BedRock ASIC, it uses the external XIO port when linked to Origin 350 Compute Modules.

An Origin 350 cannot be booted by itself without the presence of an IO9 card, it requires the IO9 to start up. If a brick lacks it, one must be installed or otherwise the brick must be numalinked.

=== CPU ===
Each brick can take dual or quad CPU configurations the same as the Tezro. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|4MB
|600,700,800
|600,700,800
|-
|8MB
|700,800
|700,800
|-
|16MB
|1000MHz
|1000MHz
|}

=== Memory ===
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Fuel, and the Tezro. There are a total of eight slots, organized into four banks of two slots. This results in a memory capacity from 512 MB to 8 GB total system memory.

All DIMMS for the Origin 350 use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

=== I/O ===
The IO9 card provides SCSI backplane support, 3.5mm Audio, and a 1Gbit Ethernet port. Three PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Origin 350 leverages NUMALink heavily to link bricks together. Each unit has a NUMALink and an XIO port, used to link various subsystems together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to eight CPU "bricks" (2 rackmount units high each) with up to four CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink3 cables going to a central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Origin 350 has a front bay for two U160 SCSI drives. It uses proprietary sleds for this purpose.

The Origin/Onyx 350, Prism, Altix 350, and Altix 450/4x00 all use the same drive carriers. These are standard parts used by a number of manufacturers, notably Intel's SC5200, SRSH4, SR1300/2300, and SR1400/2400 and Sun's v60x and v65x servers.

The units carry "Assy A65278-00x" on a sticker, where the "-00x" may end in any digit though "-005" seems common. This assembly number can be useful when searching for parts in the Internet. According to SR1300/SR2300 support documents at intel.com, the Intel accessory part number for the drive carrier is FXX2DRVCARBLK, UPC code "7 35858 14621 0" and "MM #" 835853. However note that there is some indication that Intel may recycle these accessory part numbers in the FXX- form between different models.

=== Onyx 350 ===
An Onyx 350 is an Origin 350 with a V10/V12 graphics card attached to the XIO2 slot inside, or an Origin 350 attached to a G-Brick.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator called an L3 controller.

It is recommended to use 1GHz boards in the Origin 350, not a Tezro desktop, for the reason of airflow and longevity.

=== Operating System Support ===
The Origin 350 was supported beginning with IRIX 6.5.15, and is supported through IRIX 6.5.30

[[Category:Hardware]]</text>
    <sha1>c3d491995d5d66931fdb360f2e11b931f262bfa6</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Tezro</title>
  <ns>0</ns>
  <id>55</id>
  <revision>
    <id>155</id>
    <parentid>63</parentid>
    <timestamp>2025-02-16T21:14:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3462" xml:space="preserve">For the rackmount variant of the SGI Onyx 350 branded as a Tezro, see [[Origin 350]].
[[File:Tezro-frontal.jpg|thumb|SGI Tezro, Front-profile view]]


The Silicon Graphics Tezro (styled as silicon graphics tezro) is a high-end workstation introduced by Silicon Graphics in July 2003 to replace the Octane 2. Built on the Chimera architecture, the Tezro is closely related to the Origin 350 and Onyx 350 systems offered by SGI during the same time period and shares the graphics module, node boards, drive sleds and some cooling parts. The Tezro is essentially a single-node Onyx 350 mounted on its side and connected like a sandwich to the IO backplane. The system was succeeded late in 2006 to early 2007 with the launch of the Prism. The Onyx4 launched alongside it, though that utilized the ATi developed UltimateVision. This distinction makes the Tezro the last machine designed by SGI to use an in-house graphics architecture. The Tezro is highly sought after in the collector market for its style, power, and for the distinction of being SGI's last MIPS workstation.

=== Features ===
The Tezro is powered by the MIPS R16000 series of processors and came in dual and quad CPU node boards. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|4MB
|700,800
|700,800
|-
|8MB
|700,800
|700,800
|-
|16MB
|1000MHz
|1000MHz
|}
The Tezro can take anywhere from 512M to 8G of DDR RAM, using the same proprietary DIMMs as the Fuel, Origin/Onyx 300,350, and 3000 series.

A maximum of two 300GB U160 SCSI drives can be added to the system via the front access panel using the Origin/Onyx 350-style sleds.

Tezro supports the V10 and V12 graphics options. Dual-channel options were produced, allowing up to two 1920x1200 displays. The V12 was the only **shipped** configuration, but some machines were field replaced with V10s, or have been replaced by end users to re-purpose V12s for other machines.

The IO9 card provides SCSI backplane support, 3.5mm Audio, and a 100Mbit Ethernet port. Six PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more. A DMedia card can be added to provide DMedia support as well.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== Hardware Problems ===
The fans are controlled by environmental monitoring and the system will refuse to boot if the fans do not all respond.

The 1GHz/1000MHz CPU boards are known to overheat quickly due to inadequate airflow in the case. It's advisable to set external temperature monitoring and alarms and to not run the machine unattended, as this risks VRM or CPU failure. The latter means a new node board.

=== Form Factor and Transportation ===
The Tezro measures 21 x 14 x 17 inches in L x W x H dimensions and weighs at minimum 61lbs, more if it is heavily equipped. The front access panel is very fragile, and the system should not be held by the plastics as they grow brittle with age.

The unit has wheels on the rear, allowing for easy movement on hard surfaces. It should be carried gently and preferably with the rear of the unit supporting the weight, not the sides or the front.

=== Operating System Support ===
The Tezro was supported beginning with IRIX 6.5.15, through the final 6.5.30 release.

[[Category:Hardware]]</text>
    <sha1>e5cbed6819d9adf4e3a6698860ecd5266fd52d68</sha1>
  </revision>
  <revision>
    <id>188</id>
    <parentid>155</parentid>
    <timestamp>2025-02-16T21:36:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3463" xml:space="preserve">For the rackmount variant of the SGI Onyx 350 branded as a Tezro, see [[Origin 350]].
[[File:Tezro-frontal.jpg|thumb|SGI Tezro, Front-profile view]]

The Silicon Graphics Tezro (styled as silicon graphics tezro) is a high-end workstation introduced by Silicon Graphics in July 2003 to replace the [[Octane]]. Built on the Chimera architecture, the Tezro is closely related to the Origin 350 and Onyx 350 systems offered by SGI during the same time period and shares the graphics module, node boards, drive sleds and some cooling parts. The Tezro is essentially a single-node Onyx 350 mounted on its side and connected like a sandwich to the IO backplane. The system was succeeded late in 2006 to early 2007 with the launch of the Prism. The Onyx4 launched alongside it, though that utilized the ATi developed UltimateVision. This distinction makes the Tezro the last machine designed by SGI to use an in-house graphics architecture. The Tezro is highly sought after in the collector market for its style, power, and for the distinction of being SGI's last MIPS workstation.

=== Features ===
The Tezro is powered by the MIPS R16000 series of processors and came in dual and quad CPU node boards. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|4MB
|700,800
|700,800
|-
|8MB
|700,800
|700,800
|-
|16MB
|1000MHz
|1000MHz
|}
The Tezro can take anywhere from 512M to 8G of DDR RAM, using the same proprietary DIMMs as the Fuel, Origin/Onyx 300,350, and 3000 series.

A maximum of two 300GB U160 SCSI drives can be added to the system via the front access panel using the Origin/Onyx 350-style sleds.

Tezro supports the V10 and V12 graphics options. Dual-channel options were produced, allowing up to two 1920x1200 displays. The V12 was the only **shipped** configuration, but some machines were field replaced with V10s, or have been replaced by end users to re-purpose V12s for other machines.

The IO9 card provides SCSI backplane support, 3.5mm Audio, and a 100Mbit Ethernet port. Six PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more. A DMedia card can be added to provide DMedia support as well.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== Hardware Problems ===
The fans are controlled by environmental monitoring and the system will refuse to boot if the fans do not all respond.

The 1GHz/1000MHz CPU boards are known to overheat quickly due to inadequate airflow in the case. It's advisable to set external temperature monitoring and alarms and to not run the machine unattended, as this risks VRM or CPU failure. The latter means a new node board.

=== Form Factor and Transportation ===
The Tezro measures 21 x 14 x 17 inches in L x W x H dimensions and weighs at minimum 61lbs, more if it is heavily equipped. The front access panel is very fragile, and the system should not be held by the plastics as they grow brittle with age.

The unit has wheels on the rear, allowing for easy movement on hard surfaces. It should be carried gently and preferably with the rear of the unit supporting the weight, not the sides or the front.

=== Operating System Support ===
The Tezro was supported beginning with IRIX 6.5.15, through the final 6.5.30 release.

[[Category:Hardware]]</text>
    <sha1>ac1a6ab4f53ddac8b799c1c758602ebe17ad4165</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>SGI 750</title>
  <ns>0</ns>
  <id>66</id>
  <revision>
    <id>156</id>
    <parentid>74</parentid>
    <timestamp>2025-02-16T21:14:59Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1732" xml:space="preserve">[[File:HP i2000.jpg|thumb|An HP i2000, the same computer branded by HP]]
The Silicon Graphics 750, released in May of 2001, was the first Silicon Graphics product offered with an Itanium processor. It was intended as a development platform for developers of IRIX on MIPS applications to port their software to Linux on Itanium ahead of the release of SGI's full Itanium product line. However, after poor sales and the limited performance of the first-generation Itanium processors it used became apparent, it was discontinued early, leaving SGI without an Itanium product between December 2001 and January 2003 (when the first Altix systems were introduced). A rebrand of an Intel-made Itanium developer system, it was sold by multiple manufacturers as the following products:

* Silicon Graphics 750
* Dell Precision Workstation 730
* Fujitsu-Siemens Celsius 880
* HP i2000
* IBM IntelliStation Z Pro 6894

As such, this article also applies to any of these non-SGI-sold systems. The SGI branding on the SGI 750 consists of simple stickers on the case plastic and minor software branding tweaks.

=== Specifications ===
The SGI 750 featured one or two first-generation Intel Itanium ''Merced'' processors on its processor board, up to 4GB of PC100 SDRAM on two removable Memory Expansion Cards (MECs), seven PCI expansion slots, and an AGP 4x graphics card slot fitted with an ATI XPERT 2000 PRO graphics card. It appears to have used EFI as its firmware, and included a graphical configuration tool. It was intended to be used with Linux.

=== Sources ===
http://techpubs.jurassic.nl/library/manuals/4000/007-4291-001/pdf/007-4291-001.pdf

https://www.flickr.com/photos/tbonico/3759976892

[[Category:Hardware]]
[[Category:Stubs]]</text>
    <sha1>06c312a5ac7b234377c82d41d8823c3a8739fd94</sha1>
  </revision>
  <revision>
    <id>171</id>
    <parentid>156</parentid>
    <timestamp>2025-02-16T21:25:20Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1744" xml:space="preserve">[[File:HP i2000.jpg|thumb|An HP i2000, the same computer branded by HP]]
The Silicon Graphics 750, released in May of 2001, was the first Silicon Graphics product offered with an [[Itanium]] processor. It was intended as a development platform for developers of IRIX on MIPS applications to port their software to Linux on Itanium ahead of the release of SGI's full Itanium product line. However, after poor sales and the limited performance of the first-generation Itanium processors it used became apparent, it was discontinued early, leaving SGI without an Itanium product between December 2001 and January 2003 (when the first [[Altix 350]] systems were introduced). A rebrand of an Intel-made Itanium developer system, it was sold by multiple manufacturers as the following products:

* Silicon Graphics 750
* Dell Precision Workstation 730
* Fujitsu-Siemens Celsius 880
* HP i2000
* IBM IntelliStation Z Pro 6894

As such, this article also applies to any of these non-SGI-sold systems. The SGI branding on the SGI 750 consists of simple stickers on the case plastic and minor software branding tweaks.

=== Specifications ===
The SGI 750 featured one or two first-generation Intel Itanium ''Merced'' processors on its processor board, up to 4GB of PC100 SDRAM on two removable Memory Expansion Cards (MECs), seven PCI expansion slots, and an AGP 4x graphics card slot fitted with an ATI XPERT 2000 PRO graphics card. It appears to have used EFI as its firmware, and included a graphical configuration tool. It was intended to be used with Linux.

=== Sources ===
http://techpubs.jurassic.nl/library/manuals/4000/007-4291-001/pdf/007-4291-001.pdf

https://www.flickr.com/photos/tbonico/3759976892

[[Category:Hardware]]
[[Category:Stubs]]</text>
    <sha1>6b391e0969e024fc01984be86cb837f319c3e3df</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Altix 350</title>
  <ns>0</ns>
  <id>64</id>
  <revision>
    <id>157</id>
    <parentid>72</parentid>
    <timestamp>2025-02-16T21:15:15Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4772" xml:space="preserve">The SGI Altix 350, is a rack-mounted, mid range server sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and while visually similar to the Origin 350, and sharing some ancillary parts, it is a clean break in design and runs RHEL and SLES Linux. The Altix 350 implements the IP57 processor, but follows the IP41 architecture from the earlier Altix 3000 systems. A system can include from 1 to 32 processors in up to 16 modules or bricks, with one or two NUMAlink routers connecting them. Configurations up to 8 modules can be organized in a ring topology without a router.
[[File:SGI Altix 350.jpg|thumb|Early Altix 350]]

=== Features ===
Each base module has four PCI slots across two PCI buses. The first CPU brick in a system has a single PCI slot holding an IO9 or IO10 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, audio I/O and a twisted pair Ethernet connection. The more rare IO10 is a SATA card.

The different configurations are:

* Base Module
* CMPX Expansion Module ("Cpu Memory Pci/pci-X")
* CPU Expansion Module
* NUMAlink 4 Router Module (often labeled "NL4R")

An Altix350 cannot be booted by itself without the presence of a BaseIO card. If a brick lacks it, one must be installed or otherwise the brick must be numalinked.

=== CPU ===
Each brick can take single or dual CPU configurations the same as the Prism. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="2" |CPU Configurations
|-
|CPU Cache
|Speeds (GHz)
|-
|1.5MB
|1.0, 1.4
|-
|3MB
|1.3, 1.4, 1.6
|-
|4MB
|1.4, 1.5
|-
|6MB
|1.5, 1.6
|-
|9MB
|1.6
|}

=== Memory ===
Like other first-generation Altix systems, the Altix 350 uses registered DDR DIMMs with ECC, rated at 266MHz or faster, which are commonly referred to as PC2100, PC2700, etc. Memory is organized in three banks of four DIMMs each, or twelve slots total, providing up to 24GB of RAM total per base module. DIMMs of 512MB, 1GB, and 2GB are officially supported; it is unclear as of this writing if 4GB parts will work.

=== I/O ===
The IO9 controller supports Ultra160 SCSI devices and includes an externally-accessible VHDCI port, while the IO10 controller supports SATA devices and includes a high density serial connector. Both controllers include a separate IDE interface to support optical drives.

Either IO controller provides one 1000baseT Ethernet interface. Three PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more. The BaseIO card must be installed in the bottom slot.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Altix 350 leverages NUMALink heavily to link bricks together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to sixteen CPU "bricks" (2 rackmount units high each) with up to two CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink4 cables going to one or two central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Altix 350 has a front bay for two 3.5" drives. It uses proprietary sleds for this purpose.

The Origin/Onyx 350, Prism, Altix 350, and Altix 450/4x00 all use the same drive carriers. These are standard parts used by a number of manufacturers, notably Intel's SC5200, SRSH4, SR1300/2300, and SR1400/2400 and Sun's v60x and v65x servers.

The units carry "Assy A65278-00x" on a sticker, where the "-00x" may end in any digit though "-005" seems common. This assembly number can be useful when searching for parts in the Internet. According to SR1300/SR2300 support documents at intel.com, the Intel accessory part number for the drive carrier is FXX2DRVCARBLK, UPC code "7 35858 14621 0" and "MM #" 835853. However note that there is some indication that Intel may recycle these accessory part numbers in the FXX- form between different models.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator called an L3 controller.

=== Operating System Support ===
The system can run Microsoft Windows up to Server 2008 R2 (Itanium Edition) and GNU/Linux RHEL and SLES up to versions 5 and 9 respectively.

[[Category:Hardware]]</text>
    <sha1>c2e1eaf934f95c8a837c95fce5543e74b71458c9</sha1>
  </revision>
  <revision>
    <id>172</id>
    <parentid>157</parentid>
    <timestamp>2025-02-16T21:26:04Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4776" xml:space="preserve">The SGI Altix 350, is a rack-mounted, mid range server sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and while visually similar to the [[Origin 350]], and sharing some ancillary parts, it is a clean break in design and runs RHEL and SLES Linux. The Altix 350 implements the IP57 processor, but follows the IP41 architecture from the earlier Altix 3000 systems. A system can include from 1 to 32 processors in up to 16 modules or bricks, with one or two NUMAlink routers connecting them. Configurations up to 8 modules can be organized in a ring topology without a router.
[[File:SGI Altix 350.jpg|thumb|Early Altix 350]]

=== Features ===
Each base module has four PCI slots across two PCI buses. The first CPU brick in a system has a single PCI slot holding an IO9 or IO10 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, audio I/O and a twisted pair Ethernet connection. The more rare IO10 is a SATA card.

The different configurations are:

* Base Module
* CMPX Expansion Module ("Cpu Memory Pci/pci-X")
* CPU Expansion Module
* NUMAlink 4 Router Module (often labeled "NL4R")

An Altix350 cannot be booted by itself without the presence of a BaseIO card. If a brick lacks it, one must be installed or otherwise the brick must be numalinked.

=== CPU ===
Each brick can take single or dual CPU configurations the same as the Prism. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="2" |CPU Configurations
|-
|CPU Cache
|Speeds (GHz)
|-
|1.5MB
|1.0, 1.4
|-
|3MB
|1.3, 1.4, 1.6
|-
|4MB
|1.4, 1.5
|-
|6MB
|1.5, 1.6
|-
|9MB
|1.6
|}

=== Memory ===
Like other first-generation Altix systems, the Altix 350 uses registered DDR DIMMs with ECC, rated at 266MHz or faster, which are commonly referred to as PC2100, PC2700, etc. Memory is organized in three banks of four DIMMs each, or twelve slots total, providing up to 24GB of RAM total per base module. DIMMs of 512MB, 1GB, and 2GB are officially supported; it is unclear as of this writing if 4GB parts will work.

=== I/O ===
The IO9 controller supports Ultra160 SCSI devices and includes an externally-accessible VHDCI port, while the IO10 controller supports SATA devices and includes a high density serial connector. Both controllers include a separate IDE interface to support optical drives.

Either IO controller provides one 1000baseT Ethernet interface. Three PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more. The BaseIO card must be installed in the bottom slot.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Altix 350 leverages NUMALink heavily to link bricks together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to sixteen CPU "bricks" (2 rackmount units high each) with up to two CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink4 cables going to one or two central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Altix 350 has a front bay for two 3.5" drives. It uses proprietary sleds for this purpose.

The Origin/Onyx 350, Prism, Altix 350, and Altix 450/4x00 all use the same drive carriers. These are standard parts used by a number of manufacturers, notably Intel's SC5200, SRSH4, SR1300/2300, and SR1400/2400 and Sun's v60x and v65x servers.

The units carry "Assy A65278-00x" on a sticker, where the "-00x" may end in any digit though "-005" seems common. This assembly number can be useful when searching for parts in the Internet. According to SR1300/SR2300 support documents at intel.com, the Intel accessory part number for the drive carrier is FXX2DRVCARBLK, UPC code "7 35858 14621 0" and "MM #" 835853. However note that there is some indication that Intel may recycle these accessory part numbers in the FXX- form between different models.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator called an L3 controller.

=== Operating System Support ===
The system can run Microsoft Windows up to Server 2008 R2 (Itanium Edition) and GNU/Linux RHEL and SLES up to versions 5 and 9 respectively.

[[Category:Hardware]]</text>
    <sha1>a0d81620318a887e1bad6139d402f4062e297d17</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Altix 330</title>
  <ns>0</ns>
  <id>95</id>
  <revision>
    <id>158</id>
    <parentid>109</parentid>
    <timestamp>2025-02-16T21:15:31Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2437" xml:space="preserve">[[File:Altix330.jpg|thumb|An Altix 330 stock photo]]
The SGI Altix 330, is a rack-mounted, entry level server sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and runs RHEL or SLES Linux. The Altix 330 implements the IP5X processor, but follows the IP41 architecture from the earlier Altix 3000 systems.

=== Features ===
Each base module has one PCI slot. Two gigabit ethernet ports, two SAS/Serial ATA drive bays, an external SAS/Serial ATA connector, and an optical drive are included on the system. USB for L1 and NUMALINK were also included.

The different configurations are:

* Base Module
* Compute Expansion Module
* NUMALINK Router
* PA Module

An Altix330 base module supports up to 16GB of RAM.

=== CPU ===
Each Altix 330 BCM will accommodate one or two Itanium 2 processors of the same type. However the 1.3 GHz processors were only offered in a single module, standalone configuration.
{| class="wikitable"
| colspan="2" |CPU Configurations
|-
|CPU Cache
|Speeds (GHz)
|-
|3MB
|1.3
|-
|4MB
|1.4
|-
|6MB
|1.6
|}

=== Memory ===
The Altix 330 supports registered DDR DIMMs with ECC, rated at 266MHz or faster, which are commonly referred to as PC2100, PC2700, etc. Memory throughput was claimed to peak at 10.8 GB/second.

Main memory is organized into two banks of four DIMMs each, or eight slots total, providing up to 16GB of RAM per BCM. DIMMs of 512MB, 1GB, and 2GB are officially supported; it is unclear as of this writing if 4GB parts will work.

=== NUMALink ===
The Altix 330 does not have a console serial port, and does not normally use an external L2 Controller. Instead, when a suitable USB-to-Ethernet adapter is connected to the L1 system controller on a Base Compute Module, that L1 controller becomes a hybrid L1/L2 controller for the system. After configuration the hybrid L1/L2 controller can be used to access the system console, or to control the system using the L3 software installed on a suitable Linux workstation.

Note that the L1 controller on Altix 330 Router Modules may also include the ability to become a virtual L2 controller when supplied with a suitable USB-to-Ethernet adapter.

=== Storage ===
The Altix 330 has an internal bay for two 3.5" drives.

=== Operating System Support ===
The system can run Microsoft Windows up to Server 2008 R2 (Itanium Edition) and GNU/Linux RHEL and SLES up to versions 5 and 9 respectively.

[[Category:Hardware]]</text>
    <sha1>061ba055d491811ea4b2e07c60b1c8269ac221e7</sha1>
  </revision>
  <revision>
    <id>173</id>
    <parentid>158</parentid>
    <timestamp>2025-02-16T21:26:44Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2441" xml:space="preserve">[[File:Altix330.jpg|thumb|An Altix 330 stock photo]]
The SGI Altix 330, is a rack-mounted, entry level server sold by Silicon Graphics from 2005 to 2007. This system uses [[Itanium]] 2-based processors and runs RHEL or SLES Linux. The Altix 330 implements the IP5X processor, but follows the IP41 architecture from the earlier Altix 3000 systems.

=== Features ===
Each base module has one PCI slot. Two gigabit ethernet ports, two SAS/Serial ATA drive bays, an external SAS/Serial ATA connector, and an optical drive are included on the system. USB for L1 and NUMALINK were also included.

The different configurations are:

* Base Module
* Compute Expansion Module
* NUMALINK Router
* PA Module

An Altix330 base module supports up to 16GB of RAM.

=== CPU ===
Each Altix 330 BCM will accommodate one or two Itanium 2 processors of the same type. However the 1.3 GHz processors were only offered in a single module, standalone configuration.
{| class="wikitable"
| colspan="2" |CPU Configurations
|-
|CPU Cache
|Speeds (GHz)
|-
|3MB
|1.3
|-
|4MB
|1.4
|-
|6MB
|1.6
|}

=== Memory ===
The Altix 330 supports registered DDR DIMMs with ECC, rated at 266MHz or faster, which are commonly referred to as PC2100, PC2700, etc. Memory throughput was claimed to peak at 10.8 GB/second.

Main memory is organized into two banks of four DIMMs each, or eight slots total, providing up to 16GB of RAM per BCM. DIMMs of 512MB, 1GB, and 2GB are officially supported; it is unclear as of this writing if 4GB parts will work.

=== NUMALink ===
The Altix 330 does not have a console serial port, and does not normally use an external L2 Controller. Instead, when a suitable USB-to-Ethernet adapter is connected to the L1 system controller on a Base Compute Module, that L1 controller becomes a hybrid L1/L2 controller for the system. After configuration the hybrid L1/L2 controller can be used to access the system console, or to control the system using the L3 software installed on a suitable Linux workstation.

Note that the L1 controller on Altix 330 Router Modules may also include the ability to become a virtual L2 controller when supplied with a suitable USB-to-Ethernet adapter.

=== Storage ===
The Altix 330 has an internal bay for two 3.5" drives.

=== Operating System Support ===
The system can run Microsoft Windows up to Server 2008 R2 (Itanium Edition) and GNU/Linux RHEL and SLES up to versions 5 and 9 respectively.

[[Category:Hardware]]</text>
    <sha1>4f67bb8c1bf3346c699de4304c928d87ecf63de2</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Vintage Computer Festival</title>
  <ns>0</ns>
  <id>106</id>
  <revision>
    <id>159</id>
    <parentid>130</parentid>
    <timestamp>2025-02-16T21:19:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="131" xml:space="preserve">VCF is a series of festivals and swap meets hosted around the world.

[[Category:Events]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>c8d239d3aa87762a52e79443acc8eada700446cb</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>SGUG</title>
  <ns>0</ns>
  <id>105</id>
  <revision>
    <id>160</id>
    <parentid>129</parentid>
    <timestamp>2025-02-16T21:20:17Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="166" xml:space="preserve">Silicon Graphics User Group is a community for SGI discussion that has a forum and chat system. It is one of two post [[Nekochan]] groups, the other being [[IRIXNet]]</text>
    <sha1>9a613469c2074ac531d5b6475140deadef89be15</sha1>
  </revision>
  <revision>
    <id>161</id>
    <parentid>160</parentid>
    <timestamp>2025-02-16T21:20:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="170" xml:space="preserve">Silicon Graphics User Group is a community for SGI discussion that has a forum and chat system. It is one of two post [[Nekochan.net]] groups, the other being [[IRIXNet]]</text>
    <sha1>a26c951ce6e22318873dbf1cbda60a01373d43b8</sha1>
  </revision>
  <revision>
    <id>162</id>
    <parentid>161</parentid>
    <timestamp>2025-02-16T21:20:43Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="238" xml:space="preserve">Silicon Graphics User Group is a community for SGI discussion that has a forum and chat system. It is one of two post [[Nekochan.net]] groups, the other being [[IRIXNet]]

[[Category:Communities]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>f977ad0cb4b2477d6f03bde0c40ff5670e84eb02</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Reddit</title>
  <ns>0</ns>
  <id>104</id>
  <revision>
    <id>163</id>
    <parentid>128</parentid>
    <timestamp>2025-02-16T21:21:12Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="167" xml:space="preserve">Reddit has several SGI subreddits. 

=== List of Subreddits ===
/r/sgi

/r/irix

/r/silicongraphics

[[Category:Communities]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>84207ed9dbd73b36a6619e750168b1110337ac20</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>IRIXNet</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>164</id>
    <parentid>26</parentid>
    <timestamp>2025-02-16T21:21:35Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="925" xml:space="preserve">IRIXNet, short for IRIX Network, is a Silicon Graphics-focused website, forum and archive of former hobbyist sites that was founded in 2017 by Raion (Kaz Kuroi) and Praetor (George). It was founded with the express purpose of providing a secondary Silicon Graphics site separate to [[Nekochan.net]] due to recent concerns of downtime at the time, and to facilitate open sales of commercial software. 

=== Contents ===
IRIXNet has an archive, file servers, gallery and forums. It exists as one of two English language SGI-related sites offering forums, the other being [[Silicon Graphics User Group]].

=== Association with TechPubs ===
TechPubs is owned by Raion, who also owns IRIXNet, but the purpose of Techpubs is far more focused on documentation and to serve as an SEO-friendly SGI instructional website. It does not inherit the moderation team or policies of IRIXNet.


[[Category:Communities]]
[[Category:No-Images]]</text>
    <sha1>e7040851f8cfbb3cf9df145535b10b47aaab2910</sha1>
  </revision>
  <revision>
    <id>165</id>
    <parentid>164</parentid>
    <timestamp>2025-02-16T21:21:47Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="902" xml:space="preserve">IRIXNet, short for IRIX Network, is a Silicon Graphics-focused website, forum and archive of former hobbyist sites that was founded in 2017 by Raion (Kaz Kuroi) and Praetor (George). It was founded with the express purpose of providing a secondary Silicon Graphics site separate to [[Nekochan.net]] due to recent concerns of downtime at the time, and to facilitate open sales of commercial software. 

=== Contents ===
IRIXNet has an archive, file servers, gallery and forums. It exists as one of two English language SGI-related sites offering forums, the other being [[SGUG]].

=== Association with TechPubs ===
TechPubs is owned by Raion, who also owns IRIXNet, but the purpose of Techpubs is far more focused on documentation and to serve as an SEO-friendly SGI instructional website. It does not inherit the moderation team or policies of IRIXNet.


[[Category:Communities]]
[[Category:No-Images]]</text>
    <sha1>0f1f6c2ce01f28290435c5d977ffcd59af29537f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>How to Find Commercial Software</title>
  <ns>0</ns>
  <id>107</id>
  <revision>
    <id>166</id>
    <parentid>131</parentid>
    <timestamp>2025-02-16T21:22:14Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="775" xml:space="preserve">Software for IRIX can be acquired a number of ways:

=== Requesting Software ===
IRIXNet's policies allow users to request software in the [https://forums.irixnet.org/thread-2258.html Commercial Software Request Megathread] where users can share such things over private messaging.

=== Purchasing Software ===
IRIXNet and SGUG both have forums for selling software. Additionally, eBay and other places are sources for this. 

=== Dealing with the Licenses ===
Two forms of licensing for IRIX were common: [[Flexlm]] and dongles. Dealing with the former is just a matter of getting a valid license and placing it into the license.dat. Dealing with the latter necessitates using cracks to patch the executable.

[[Category:Tutorials]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>eafe46233223ec8cdd677878c5605bcc8033ab41</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>IRIX 101</title>
  <ns>0</ns>
  <id>12</id>
  <revision>
    <id>167</id>
    <parentid>16</parentid>
    <timestamp>2025-02-16T21:22:54Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5332" xml:space="preserve">This guide aims to educate new users to IRIX about the differences between IRIX and other UNIX and Unix-like systems. This includes through FAQs, explanations of how some parts of the OS work, and how a new user can adjust to these changes easily.

=== A Brief History of IRIX ===
IRIX began life as an evolution of two earlier projects, GL2 and RISCOS (a product by MIPS Computer Systems, not the Acorn RISC OS), the latter of which was acquired by Silicon Graphics in 1992. GL2 code from the 68000-based IRIS machines was ported to System V R3, making 4D1-3.x - the immediate predecessor of IRIX de jure, but defacto IRIX under the hood. 4D1-3.x utilized NeWS in the form of 4Sight, replacing MEX, the windowing system on GL2. When SGI acquired MIPS Computer Systems, RISCOS had many things taken from it to form IRIX 4, which used XSGI and the familiar 4DWM instead of 4Sight. IRIX now steadily advanced, with 6.x introducing XFS, and 6.5 introducing many more HPC elements to the OS. The last major release was 6.5 in 1998, but the OS continued minor development until 2006 with the discontinuation of all MIPS development by SGI and the migration to IA-64 and GNU/Linux, ending the reign of IRIX and effectively relegating it to maintenance mode.

Throughout the 1990s, IRIX was influential in many industries such as HPC, education, scientific, 3D graphics (Autodesk Maya began life as PowerAnimator on IRIX for example) and music production. This legacy is a huge contribution to continued hobbyist development of IRIX.

=== Frequently Asked Questions ===
1. Is IRIX related to GNU/Linux?

IRIX's XFS filesystem was ported to the Linux kernel and continues to be a major filesystem on GNU/Linux. Beyond that, IRIX is entirely different, predating Linux by years of development.

2. What systems does IRIX run on?

IRIX runs on MIPS workstations produced by SGI, and a modified version of it underpins UNICOS/mp on the Cray X1 and X1E. Other than that, it cannot run on anything else.

3. What does IRIX use for GUI?

IRIX, like most UNIX systems uses X11, a proprietary variant called XSGI, and the window manager is called 4DWM - standing for 4D Window Manager (early SGI machines were called 4D, and this also hearkens back to 4Sight and 4D1, the old name for IRIX).

4. Why are machines that run IRIX expensive?

There are no new machines being produced, and high-end machines are in short supply. Less expensive machines can be had. We do not recommend using eBay to search, as the prices are usually extremely inflated.

5. What shell does IRIX use? It doesn't behave like Bash!

Most UNIX do not use bash. IRIX uses tcsh and ksh as shells. tcsh is the one that has many of the features users are after (history, tab completion of arguments, repeat last argument (!$, not ESC-.), and thus the recommended interactive shell. However, should a user prefer it is possible to use bash from Nekoware, or other sources. It's not recommended to replace the root shell with bash, however.

6. What startup system does IRIX use?

IRIX uses a customized System V init. It is not the same as GNU/Linux's former default (sysvinit).

7. Where are eth0, sda1, and why does ifconfig show nothing unless I append -a?

IRIX, similar to BSDs and System V UNIX OSes, names devices by driver, not type. The disk naming scheme is similar to Solaris and illumos, /dev/dsk/dksXdXsX, or disk, scsi bus id, drive id, slice ID. ifconfig shows nothing unless -a is hit because it's not the same code as GNU/Linux.

8. Where can I get the source to IRIX?

IRIX is closed source, and there was no major release of the source during its lifetime. Community efforts to free it from limbo are ongoing.

9. Is USB supported?

Only HID, USB audio and some controllers are supported. No USB mass storage or cameras or anything like that.

10. Can I mount an ISO of IRIX software?

No, not within IRIX. IRIX has no loopback filesystem support. Additionally, IRIX software is distributed on EFS CDs, not Joliet/rockridge/iso9660 (the format that is specified by .iso) so don't use .iso - use .efs or .img

11. My backspace key doesn't work.
This is common on some configurations. To fix, type the following sequence into a shell: &lt;code&gt;stty erase CTRL-V BACKSPACE&lt;/code&gt; the caps indicate actual keys to hit, not actual things to type. This should result in either stty erase

H or stty erase
? or something similar.
12. CTRL-C doesn't do SIGINT

Fixable. &lt;code&gt;stty intr ^C&lt;/code&gt;

Both 11 and 12 can be permanently solved by adding those commands to .cshrc or .bashrc or .profile, depending on the shell used and such.

13. Where is nano?

GNU nano never was packed with IRIX. Get used to using vi, that's the default commandline editor. There's jot as well, a graphical editor, and nedit. Nano is available from many distributions.

14. Can IRIX be emulated?

MAME currently supports (slow) emulation of IRIX. Do not use qemu-irix - it's not designed to run actual IRIX software, it's designed as a hack for N64 devs to use the IDO/MIPSPro compilation suite to reverse engineer N64 games.

15. Inst doesn't help with dependencies

IRIX is from an era where dependencies needed to all be supplied at once or in-order for a package manager to work. It does not currently support dependency resolution at all.


[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>9b7bf17163c5f424e85965cfb0141ffca45582f0</sha1>
  </revision>
  <revision>
    <id>168</id>
    <parentid>167</parentid>
    <timestamp>2025-02-16T21:23:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5345" xml:space="preserve">This guide aims to educate new users to IRIX about the differences between IRIX and other UNIX and Unix-like systems. This includes through FAQs, explanations of how some parts of the OS work, and how a new user can adjust to these changes easily.

=== A Brief History of IRIX ===
IRIX began life as an evolution of two earlier projects, [[GL2]] and [[RISC/OS]] (a product by MIPS Computer Systems, not the Acorn RISC OS), the latter of which was acquired by Silicon Graphics in 1992. GL2 code from the 68000-based IRIS machines was ported to System V R3, making [[4D1-3.x]] - the immediate predecessor of IRIX de jure, but defacto IRIX under the hood. 4D1-3.x utilized NeWS in the form of 4Sight, replacing MEX, the windowing system on GL2. When SGI acquired MIPS Computer Systems, RISCOS had many things taken from it to form IRIX 4, which used XSGI and the familiar 4DWM instead of 4Sight. IRIX now steadily advanced, with 6.x introducing XFS, and 6.5 introducing many more HPC elements to the OS. The last major release was 6.5 in 1998, but the OS continued minor development until 2006 with the discontinuation of all MIPS development by SGI and the migration to IA-64 and GNU/Linux, ending the reign of IRIX and effectively relegating it to maintenance mode.

Throughout the 1990s, IRIX was influential in many industries such as HPC, education, scientific, 3D graphics (Autodesk Maya began life as PowerAnimator on IRIX for example) and music production. This legacy is a huge contribution to continued hobbyist development of IRIX.

=== Frequently Asked Questions ===
1. Is IRIX related to GNU/Linux?

IRIX's XFS filesystem was ported to the Linux kernel and continues to be a major filesystem on GNU/Linux. Beyond that, IRIX is entirely different, predating Linux by years of development.

2. What systems does IRIX run on?

IRIX runs on MIPS workstations produced by SGI, and a modified version of it underpins UNICOS/mp on the Cray X1 and X1E. Other than that, it cannot run on anything else.

3. What does IRIX use for GUI?

IRIX, like most UNIX systems uses X11, a proprietary variant called XSGI, and the window manager is called 4DWM - standing for 4D Window Manager (early SGI machines were called 4D, and this also hearkens back to 4Sight and 4D1, the old name for IRIX).

4. Why are machines that run IRIX expensive?

There are no new machines being produced, and high-end machines are in short supply. Less expensive machines can be had. We do not recommend using eBay to search, as the prices are usually extremely inflated.

5. What shell does IRIX use? It doesn't behave like Bash!

Most UNIX do not use bash. IRIX uses tcsh and ksh as shells. tcsh is the one that has many of the features users are after (history, tab completion of arguments, repeat last argument (!$, not ESC-.), and thus the recommended interactive shell. However, should a user prefer it is possible to use bash from Nekoware, or other sources. It's not recommended to replace the root shell with bash, however.

6. What startup system does IRIX use?

IRIX uses a customized System V init. It is not the same as GNU/Linux's former default (sysvinit).

7. Where are eth0, sda1, and why does ifconfig show nothing unless I append -a?

IRIX, similar to BSDs and System V UNIX OSes, names devices by driver, not type. The disk naming scheme is similar to Solaris and illumos, /dev/dsk/dksXdXsX, or disk, scsi bus id, drive id, slice ID. ifconfig shows nothing unless -a is hit because it's not the same code as GNU/Linux.

8. Where can I get the source to IRIX?

IRIX is closed source, and there was no major release of the source during its lifetime. Community efforts to free it from limbo are ongoing.

9. Is USB supported?

Only HID, USB audio and some controllers are supported. No USB mass storage or cameras or anything like that.

10. Can I mount an ISO of IRIX software?

No, not within IRIX. IRIX has no loopback filesystem support. Additionally, IRIX software is distributed on EFS CDs, not Joliet/rockridge/iso9660 (the format that is specified by .iso) so don't use .iso - use .efs or .img

11. My backspace key doesn't work.
This is common on some configurations. To fix, type the following sequence into a shell: &lt;code&gt;stty erase CTRL-V BACKSPACE&lt;/code&gt; the caps indicate actual keys to hit, not actual things to type. This should result in either stty erase

H or stty erase
? or something similar.
12. CTRL-C doesn't do SIGINT

Fixable. &lt;code&gt;stty intr ^C&lt;/code&gt;

Both 11 and 12 can be permanently solved by adding those commands to .cshrc or .bashrc or .profile, depending on the shell used and such.

13. Where is nano?

GNU nano never was packed with IRIX. Get used to using vi, that's the default commandline editor. There's jot as well, a graphical editor, and nedit. Nano is available from many distributions.

14. Can IRIX be emulated?

MAME currently supports (slow) emulation of IRIX. Do not use qemu-irix - it's not designed to run actual IRIX software, it's designed as a hack for N64 devs to use the IDO/MIPSPro compilation suite to reverse engineer N64 games.

15. Inst doesn't help with dependencies

IRIX is from an era where dependencies needed to all be supplied at once or in-order for a package manager to work. It does not currently support dependency resolution at all.


[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>19212f5e4a80f5fb345ba81ee1ce5519f4abc01c</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Installing IRIX</title>
  <ns>0</ns>
  <id>13</id>
  <revision>
    <id>169</id>
    <parentid>17</parentid>
    <timestamp>2025-02-16T21:24:14Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="852" xml:space="preserve">It is recommended to install IRIX via a network for ease of use. IRIX has a rather unique and comprehensive network installing method, and as a result of it's convenience, performance and utility, many users have created guides on how to do it. This serves as the meta hub. 

=== General ===
The following network protocols must be used to network install IRIX:

* rsh
* tftp
* bootp

The host must in most cases be a UNIX compatible with UNIX permissions, on the same LAN. IRIX PROMs do not possess routing, ICMP echoes (It cannot respond to pings), or the ability to take HTTP or rsync.

=== Guides ===
This subsection offers specific guides for installation with various host operating systems.

==== IRIX ====

* [[IRIX Install using IRIX Host]]

==== NetBSD ====

* [[IRIX Install using NetBSD Host]]

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>a0f87539a772dd9900719bf14f1bf42a6a70b71e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>IRIX Setup 101</title>
  <ns>0</ns>
  <id>7</id>
  <revision>
    <id>170</id>
    <parentid>10</parentid>
    <timestamp>2025-02-16T21:24:35Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12464" xml:space="preserve">For newcomers to IRIX, setting up IRIX for the first time can be daunting. This aims to break it down into selective, easy-to-follow sections for a post-install IRIX.

=== Forenotes ===
Due to specificity of various hardware and IRIX versions, this guide primarily assumes IRIX 6.5.21+ and that the user is interested in running Nekoware, optxeno, or another product offered on IRIXNet. It is advised to go into this understanding what the goals of the user are exactly.

Per the Style Guide all root commands will be prefixed with #, all user-level commands will be prefixed with % (for the tcsh shell).

=== First Steps ===

==== Securing root ====
Either login on the login screen to root, or serial in via root. Open a terminal window by clicking Desktop - &gt; Open Unix Shell. This is the root shell of the account, and for clarity sake, most commands will be performed via terminal. Type &lt;code&gt;# passwd&lt;/code&gt; and set a secure password for the root user. If doing this from GUI (i.e. EZSetup, this will cover most of the important settings covered there) be warned IRIX will not accept passwords greater than 8 chars in length. From the commandline, there is no such limitations.

==== Network Setup ====
A detailed article can be found at Network Setup.

==== Date and Time ====
Again, a detailed article can be found at Keeping Time

==== Move $HOME for root ====
Now it is necessary to make a space for root. Due to IRIX's default install, root's home directory is effectively /, the root of the filesystem. '''This is bad. Do not skip this step.'''

Home directories are defined in &lt;code&gt;/etc/passwd&lt;/code&gt;. First, make the directory: &lt;code&gt;# mkdir /root; chmod go-wrx /root&lt;/code&gt; And then update the root line to look like so: &lt;code&gt;root::0:0:Super-User:/root:/bin/tcsh&lt;/code&gt; This can be automated (carefully) with a perl, awk, or sed command, but be careful.

Now clean up: &lt;code&gt;# cd /; rm -rf Desktop dumpster .Sgiresources .cshrc .login .profile .varupdate .wshttymode .desktop-IRIS .desktophost&lt;/code&gt;

Log out and log back in again.

=== Securing IRIX ===

==== Lock unsafe accounts ====
IRIX by default is installed with several accounts without passwords. Checking this is easy: &lt;code&gt;# passwd -as&lt;/code&gt;

Locking the accounts on a normal IRIX install is easy:

&lt;code&gt;# foreach account (lp EZsetup nuucp demos guest OutOfBox sys adm sysadm cmwlogin auditor dbadmin sgiweb 4Dgifts); passwd -l $account; end&lt;/code&gt;

==== Creating a user account ====
Next, create a user account for normal usage, as running as root 24/7 is dangerous. It's easily and safely done using tools in the privbin: &lt;code&gt;# /usr/sysadm/privbin/addUserAccount -l username -S `which tcsh` -H /usr/people/username -C -u 1034 -g 20&lt;/code&gt;

The above example will create a user called '''username''' with a default shell of tcsh, a home directory of &lt;code&gt;/usr/people/username&lt;/code&gt; (/home is NOT a thing on IRIX), create the directory (-C flag) with a uid of 1034 and membership in the user group (ID 20). It may also be advisable to create a group with the same username created by the command above, however that requires manually adding a group to &lt;code&gt;/etc/group&lt;/code&gt; and editing permissions on the home directory. This may be covered in a future installment.

==== Enable Shadow Passwords ====
By default IRIX uses crypt() hashes in /etc/passwd

This is now discouraged and insecure, so it is preferred to enable /etc/shadow. Run &lt;code&gt;pwconv&lt;/code&gt; to enable it.

==== Edit system defaults ====
The file &lt;code&gt;/etc/default/login&lt;/code&gt; controls primary login behavior. Edit the files options to look something akin to this:&lt;pre&gt;
CONSOLE=/dev/console

PASSREQ=YES

ALTSHELL=YES

MANDPASS=YES

UMASK=027

TIMEOUT=60

DISABLETIME=300

MAXTRYS=3

LOGFAILURES=4

IDLEWEEKS=2

PATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11:

SUPATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/etc:/usr/etc:/usr/bin/X11:

SYSLOG=ALL

INITGROUPS=YES

LANG=C

SVR4_SIGNALS=NO

LOCKOUT=4

LOCKOUTEXEMPT=root
&lt;/pre&gt;Note that it is a good opportunity to add extra pathnames that all users will have in PATH. Examples include /usr/nekoware/bin, /opt/xeno/bin, et cetera.

chmod the file to 444 next: &lt;code&gt;# chmod 444 /etc/default/login&lt;/code&gt;

==== File Alteration Monitor ====
For security reasons, edit &lt;code&gt;/etc/fam.conf&lt;/code&gt; to have local_only = true instead of local_only = false.

==== Disable Vulnerable Network Services ====
The following network services are wholly unnecessary for most installations and can be disabled with the following command string:&lt;pre&gt;
# chkconfig sgi_apache off; chkconfig webface_apache off; chkconfig appletalk off; \

chkconfig timed off; chkconfig timeslave off; chkconfig esp off; chkconfig ipaliases off; \

chkconfig ypmaster off; chkconfig yp off; chkconfig sendmail off; chkconfig sendmail_cf off; \

chkconfig webface off; chkconfig named off; chkconfig rsvpd off; chkconfig privileges off
&lt;/pre&gt;Additionally, disabling the following services in &lt;code&gt;/etc/inetd.conf&lt;/code&gt; is prudent, except telnet if an ssh server isn't installed yet, and the system is a server. If that's the case, hold off on that one:&lt;pre&gt;
finger

bootp

tftp

echo

telnet

ftp

discard

chargen

daytime

time

rstatd

walld

rusersd

rquotad

sprayd

ttdbserverd

shell

exec

http

wn-http

ntalk

mountd

sgi_mountd

rexd

bootparam

ypupdated

sgi_videod

sgi_toolkitbus

sgi_snoopd

sgi_pcsd

sgi_pod

sgi_espd

sgi-esphttp

tcpmux/sgi_scanner
&lt;/pre&gt;Some of the above can be re-enabled depending on what is necessary, but the esp ones should not be re-enabled.

==== Secure the X server ====
Edit &lt;code&gt;/var/X11/xdm/xdm-config&lt;/code&gt; and change the DisplayManager*authorize line to read: &lt;code&gt;DisplayManager*authorize: on&lt;/code&gt;

==== Tune the kernel for security ====
Changing these if they are not in use is prudent:&lt;pre&gt;
# printf 'y' | systune ipforwarding 0

# printf 'y' | systune ip6forwarding 0

# printf 'y' | systune icmp_dropredirects 1

# printf 'y' | systune tcp_2msl 60

# printf 'y' | systune allow_brdaddr_srcaddr 0

# printf 'y' | systune tcpiss_md5 1

# printf 'y' | systune restricted_chown 1

# printf 'y' | systune ncargs 131072

&lt;/pre&gt;run &lt;code&gt;# /etc/autoconfig -vf&lt;/code&gt; to rebuild the kernel, and then reboot for full changes to take effect.

==== Install Patches ====
A collection of patches obtained from user backups of sgi.com's support centre is here: &lt;nowiki&gt;http://ftp.irixnet.org/sgi-irix/patches/&lt;/nowiki&gt;

Install all patches for the IRIX version being ran. (inst will not install irrelevant patches on the system).

=== Customizing IRIX ===
Now that security is improved, the actual fun can begin to customizing the IRIX experience.

==== Setup flexlm ====
Place licenses for products in /var/flexlm/license.dat. Softwindows and a few others use different locations. There is a license file in the wiki as well. (search for it!)

==== Enable 24 bit X ====
Unless the graphics in the system are 8-bit (such as an Indy with an XL/8 card), enabling Truecolor will improve the user experience. Edit &lt;code&gt;/var/X11/xdm/Xservers&lt;/code&gt; to be &lt;code&gt;:0 secure /usr/bin/X11/X -bs -nobitscale -c -class TrueColor -depth 24 -solidroot sgilightblue -cursorFG red -cursorBG white&lt;/code&gt;

==== Enable scrollwheel. ====
IRIX by default can't use a scroll wheel. This can be rectified in the kernel:

&lt;code&gt;# systune pcmouse_mode 2&lt;/code&gt;

This sets the scroll wheel to work as on a PC. Mode 3 will set any additional buttons on the mouse to scroll. (it only detects 2 extra buttons)

==== Reduce gamma ====
Set gamma with the following command as root: &lt;code&gt;gamma 1.2&lt;/code&gt; or another value. This will lower the default to a more natural level.

==== Custom tcsh prompt ====
tcsh is a fast, simple UNIX shell that supports most of the same features as bash from an interactive standpoint, and is faster at startup.

Here is a configuration file for root:&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${red}%n${blue}@%m ${yellow}%~ ${red}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;


This sets a red prompt as a reminder. The colors can be changed in the prompt section to one's liking, just don't mess with color values.&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${cyan}%n${blue}@%m ${yellow}%~ ${green}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;And here is a version that is used for normal users.

PATH should be set using &lt;code&gt;setenv PATH '/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11'&lt;/code&gt; and more paths added with a colon-delimited list in the rc file

==== Setting Desktop parameters ====
Use "Desktop-&gt;Customize-&gt;Utilities" from the toolchest menu to specify default applications. Using the full path is necessary. "Desktop-&gt;Customize-&gt;Icons" from the toolchest menu will set the icon size and enable the global setting "Open in Place" which prevents the file manager from creating a new window when opening a new directory.

==== Xdefaults file ====
Here is a sample configuration that dates to the Nekochan.net era:&lt;pre&gt;
*clientDecoration: +resizeh +border +minimize +maximize +menu

*DesksOverview*clientDecoration: none

4Dwm*clock*clientDecoration: none

Overview.geometry: +10-10

Overview*viewWindowName: true

Overview*Frame.marginHeight: 1

Overview*Frame.marginWidth: 1

4Dwm*interactivePlacement: False

4DWm*clientAutoPlace: False

4Dwm*usePPosition: True

4Dwm*positionOnScreen: True

4Dwm*iconImageBackground black

4Dwm*iconImageForeground: white

4Dwm*iconPlacement: left top tight

4Dwm*iconPlacementMargin: 1

4Dwm*resizeBorderWidth: 1

4Dwm*frameBorderWidth: 1

4Dwm*SG_frameOutline: false

4Dwm*SG_titleOutline: false

4Dwm*SG_titlePadding: 0

4Dwm*SG_useDecals: false

4Dwm*iconDecoration: label image
&lt;/pre&gt;The desktop can be heavily customized as needed. To customize 4Dwm, read its manpage

==== Setting up SSH ====
IRIX came with a very old OpenSSH version, and Nekoware has OpenSSH as well. However, these are no longer maintained. A better option is available at SSH Setup on IRIX 6.5.

==== Amend toolchest ====
A full explanation of toolchest is available on its manpage. toolchest reads the following files:&lt;pre&gt;
/usr/lib/X11/system.chestrc

~/.chestrc

~/.auxchestrc

/usr/lib/X11/nodesktop.chestrc

/usr/lib/X11/app-chests/*.chest

/usr/lib/X11/app-defaults/Toolchest

/usr/lib/X11/remote.chestrc

The first three are relevant to most users. To remove entries, remove Itemname in a ~/.auxchestrc is sufficient. Creating entries is easy as well:

menu ToolChest

{

"My Favorite Things" f.menu mystuff

}

menu mystuff

{

"dolphins" f.exec "/usr/demos/bin/atlantis"

"Test Program" f.exec "source ~/.variables;~/testprog"

"games" f.menu mygames

}

menu mygames

{

"flight simulator" f.exec /usr/demos/bin/flight

"arena" f.exec /usr/demos/bin/arena

}
&lt;/pre&gt;Is the manpage example.

==== Setting Backgrounds ====
An article on this is available at Setting Backgrounds

=== Wrapping up ===
This is the end of IRIX Setup 101. For practical reasons this ends most common "first time" setup questions and was patterned after the popular, though poorly-written "IRIX Installation and Customization". Further guides will explore how to perform more advanced configurations.

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>6f87c5c0007110310692f80f37b0ab89d9405b57</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Itanium</title>
  <ns>0</ns>
  <id>109</id>
  <revision>
    <id>174</id>
    <timestamp>2025-02-16T21:28:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Itanium, also known as IA-64 and IPF (Itanium Processor Family), is a RISC-like CPU architecture developed by HPE and Intel in the 1990s to serve as a high end, 64-bit, RISC processor architecture to replace HP's PA-RISC."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="221" xml:space="preserve">Itanium, also known as IA-64 and IPF (Itanium Processor Family), is a RISC-like CPU architecture developed by HPE and Intel in the 1990s to serve as a high end, 64-bit, RISC processor architecture to replace HP's PA-RISC.</text>
    <sha1>710e2bb87ddf6aa1bee0d9e3053c5becf2aa8c3c</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>68k-based SGIs (IRIS Series)</title>
  <ns>0</ns>
  <id>98</id>
  <revision>
    <id>175</id>
    <parentid>140</parentid>
    <timestamp>2025-02-16T21:29:18Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="395" xml:space="preserve">The earliest SGI systems were 68000-68020 powered graphics terminals and workstations running [[GL2]], a System V UNIX with an unusual for the time focus on graphics. Multibus standard powered machines, they were similar to Sun Multibus systems in many respects.

They were replaced by the [[Professional IRIS]] series of systems.

[[Category:Hardware]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>0cb7dd99b5c9e23fea72dba7551954b8fd24de9c</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Personal IRIS</title>
  <ns>0</ns>
  <id>18</id>
  <revision>
    <id>176</id>
    <parentid>142</parentid>
    <timestamp>2025-02-16T21:29:51Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4791" xml:space="preserve">The Personal Iris was introduced in 1988 as low end workstation to the IRIS 4D series based on MIPS RISC microprocessors. A model name consists of "4D/" and a code designating the CPU and graphics type. The models replaced the "Twin Tower" style [[Professional IRIS]] series on the low end market, with the [[Power Series]] taking the higher end market. All Personal IRIS systems use a 32-bit MIPS I core and share some parts commonality with the R3000 Indigo in the 30 and 35 models. The last model (4D/35) was introduced in 1991 and presumably sold through 1993 with the release of the Indy heralding the end of the IRIS line.
[[File:PersonalIris.jpg|thumb|A 4D/35 owned by CB_HK of IRIXNet]]

=== Models ===
The series came in four models differentiated by badging, and the contents of the system module inside the case. No major external differences are otherwise shown. Between the 4D/2x and the 4D/3x systems are major differences. The latter one uses a totally different system board which besides faster processors includes a newly designed memory interface that allows much higher bandwidth and a larger amount of main memory. The system bus of the newer boards is clocked at 30 MHz instead of 10 MHz.
{| class="wikitable"
|Model
|CPU board
|CPU
|Maximum Memory
|-
|4D/20
|IP6
|MIPS R2000 12.5 MHz
|32MB
|-
|4D/25
|IP10
|MIPS R3000 20 MHz
|32MB
|-
|4D/30
|IP14
|MIPS R3000 30 MHz
|128MB
|-
|4D/35
|IP12
|MIPS R3000 36 MHz
|128MB
|}
The 20 and 25 models use industry standard 30-pin SIMMs. The 30 and 35 models use the same RAM modules as the Indigo R3000.

=== Graphics ===
The Personal IRIS had either a Datastation (Server) configuration, or they could utilize VME-based Eclipse or Express graphics, the latter only being usable on the 30 and 35 models due to a common architecture with the [[IRIS Indigo]]

=== Peripherals ===
The Personal IRIS, unlike later SGIs, does NOT possess support for PS/2 and uses the 4D-style DB9 keyboards used by the Personal/Professional IRIS series. To use PS/2 peripherals necessitates an adapter.

Personal IRIS models 4D/20 and 4D/25 have basic audio capabilities onboard. For audio in 4D/30 and 4D/35 an optional board is required that is plugged into a special slot on the mainboard. That additional board is called Magnum Audio Option and offers 16bit/stereo audio instead of the 8bit/mono audio that was offered on the earlier Personal Iris models.

The Personal IRIS has a built in SCSI controller that supports the internal as well as the external SCSI devices. The SCSI connector is located on the back of machine itself (just right of the E-Module) and is also covered by the plastic skin. The internal drives connect to the same SCSI chain that is also available via that external centronics SCSI port. The SCSI controller is narrow SCSI, Western Digital 33C93A.

All Personal IRIS systems allow the owner to install double height 6U VME devices. The VME interface of the Personal Iris also supports busmaster devices which may directly access the main memory of the computer. Only the 4D/30 and 4D/35 models allow VME block transfer due to a new peripheral controller on the system board.

=== Operating System Support ===
The Personal IRIS line was available during the "IRIX 3.x" era, but more contemporaneously called 4D1-3.x UNIX era. Support continued into IRIX 4.x and 5.x, and was removed along with all other 32-bit options by 5.3.

=== Hardware Problems ===

==== Power Supply ====
Power supply problems are not uncommon with these systems. Unplug the power cord, then open the opposite side of the E-Module and remove the sheetmetal. The power supply has 2 replaceable fuses which are worth to check as well as the proper cabling. One fuse is on the small daughtercard, the other is next to that card and usually covered with a blue plastic cap.

==== Onboard Battery ====
Signs of failure: The system fails to boot and returns to PROM after issuing "Can't set tod clock"

This problem has so far been seen only on the later Personal Iris models (4D/30 and 4D/35). The earlier systems may not be affected and just boot with a faulty date/time.

While there also may be other causes, the by far most likely is an empty battery on the CPU board. The original battery is a 3V coin cell made by Duracell (DL2450). The battery is socketed so replacing it doesn't require any soldering. The cost of the battery is approximately 3 USD / 2 EUR.

==== 4MB Memory Modules ====
Signs of failure: System doesn't work when more than one set of 4MB modules is installed.

This is a known problem and a flaw in the systems hardware of 4D/30 and 4D/35 systems which can not be fixed. The bottom line is, that only one 16MB kit (4x4MB) may be installed - there is no limitation regarding 8MB (4x2MB) or 32MB (4x8MB) kits.

[[Category:Stubs]]</text>
    <sha1>c152465c16789c0e2088b6d5d48259ec4eb87b6e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>IRIS Indigo</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>177</id>
    <parentid>143</parentid>
    <timestamp>2025-02-16T21:31:13Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5588" xml:space="preserve">The SGI Indigo (Also known widely as the IRIS Indigo) is a line of high end workstations using the MIPS processor family released as a successor to the [[Personal IRIS]] series.

The Indigo R4000 was also the first SGI workstation that that featured the 64bit R4000 RISC CPU on the desktop, the first SGI in general using the new CPU was the [[Crimson]]. The Indigo offers builtin audio capabilities and comes in a very well designed and space efficient chassis. With one of the Express graphics options it offers accelerated 3D graphics.
[[File:Indigo2-mag.jpg|thumb|IRIS Indigo owned by CB_HK]]

=== Features ===

* One 32-bit R3000 at 33MHz or a R4000 at 100MHz, or a R4400 at 150MHz.
* A maximum of 96MB RAM on R3000 boards (IP12), and 384MB on R4x00 boards (IP20)
* Two GIO32 slots for expansion boards.
* A Motorola 56000 DSP-driven Audio system.
* Seven different graphics options:

* Entry (LG1/2 board)
* Express (XS8, XS24, XS24Z, XZ, Elan)

=== Peripherals ===
The Indigo, unlike later SGIs, does NOT possess support for PS/2 and uses the same keyboard as the SGI Onyx and Crimson. To use PS/2 peripherals necessitates an adapter.

The graphics board uses the 13w3 connector which requires a SOG compliant monitor.

=== Storage ===
All Indigo systems have three drive bays for internal 3.5" SCSI devices that have to be mounted on special drive sleds to be used in the systems. The upper two of them can be accessed from the outside through a small door which makes them usable for removable media drives. To remove any of the three drives the front plate has to be removed which is impossible if the system is secured with the locking bar.

The skins of the Indigo are colored in a dark blue which has a decent hint of purple to it. On R3000 Indigos the type of the graphics option the machine was shipped with was printed on the front door. On R4000 a small badge was used that in addition to the name of the graphics option included "4000" to denote the faster CPU type.

=== Operating System Support ===
The Indigo when first introduced was based on the R3000 microprocessor. Support for this system was added to 4D1-4.x from beginning on (4D1-4.0). Support for Elan, XZ and XS graphics was added shortly thereafter in 4D1-4.0.2. Next support for the new R4000 based model was added in 4D1-4.0.5E.

General support for the Indigo can be found in the all platform releases of IRIX 5.x. Only the R4000 models were supported by IRIX 6.2 and IRIX 6.5. The support for the remaining legacy systems like the Indigo R4000 was dropped after 6.5.22 making IRIX 6.5.22 the last version to support any of these systems.
[[File:Indigo-front-1000.jpg|thumb|IRIS Indigo from the front]]

=== Hardware Problems ===
The Indigo does have a number of potential failures:

==== Battery Failure ====
Signs of failure: The system fails to boot and repeats the message "Can't set tod clock"

This error is very common these days and it occurs during boot time. It usually means that the onboard battery is empty and that the system can't set it's clock. It is not fatal and some systems even recover when they are run for a while. This error does not occur while the system is running.

The original battery used is a Tadiran TL-5186 3.6V battery. Current replacements are the Sonnenschein SL-340 or SL-840. Both can be installed in the same place as the original battery of the Indigo.

In the long run a cheaper solution is to wire a socket for a generic button cell to the battery connectors on the main board. The socket could be fixed on one of the GIO32 bus placeholders. The Indigo will work just fine with a standard and much cheaper 3 V button cell (like a CR2032).

==== Memory Controller ====
Signs of failure: While booting the system displays a message like "Warning: Revision C Memory Controller (MC) chip needed in order to properly operate with SIMMS of this type."

When upgrading memory on an R4000 Indigo IRIX might issue the above warning if there is no Rev C memory controller installed in the system (This can be checked using /usr/gfx/gfxinfo). If all memory is detected (i.e. shown in hinv) and there are not unusual problems with the system since the upgrade it should be safe to ignore the message. It was added when there were bugs in some memory modules. The upgraded Rev C memory controller contains a workaround for these bugs, but as these have also long been fixed there should be no problems today - even with older MCs.

In later IRIX the warning message has been worded differently: "WARNING: You may need a memory controller revision C because of the type of simms installed. If you don't experience any memory errors you won't need MC revision C"

==== Bad eaddr ====
Signs of failure: The system complains about a bad ethernet address (ff:ff:ff:ff:ff:ff).

In general this means that the EEPROM that contains the hardware ethernet address is dead or contains invalid data. It is an 8 pin MiniDIP serial EEPROM (93C56) which is socketed on the backplane.

In many cases the reason is, that in the Indigo different CPU boards (IP20, then IP12) were used. The location of the address is different between the two boards and is properly relocated when a system is upgraded from IP12 to IP20. When the IP12 is placed back in the system the MAC address is erased.

A possible solution is to place the IP12 in the system and reset the mac address from the PROM monitor using the eaddr command - the IP20 doesn't allow that. After that the system can be used with the IP12 board or upgraded to IP20 which will relocate the address once again.

[[Category:Hardware]]</text>
    <sha1>b7ffb6be0fc5be3b1f05e7671e08d24f43154762</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Crimson</title>
  <ns>0</ns>
  <id>42</id>
  <revision>
    <id>178</id>
    <parentid>144</parentid>
    <timestamp>2025-02-16T21:31:47Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5140" xml:space="preserve">The IRIS Crimson or simply Crimson is the partial successor to the [[Power Series]], first released in 1992. It was the first SGI workstation released with a 64-bit processor.
[[File:IRIS Crimson.jpg|thumb|A typical IRIS Crimson]]
The Crimson was a member of Silicon Graphics' IRIS 4D series of deskside systems; it was also known as the 4D/510 workstation. It was similar to other SGI IRIS 4D deskside workstations, and could utilize a wide range of graphics options (up to RealityEngine). It was also available as a file server with no graphics. 

=== Features ===

* One superpipelined MIPS 100 MHz R4000 or 150 MHz R4400 processor.
* Seven high performance 3D graphics subsystem options deliver performance and features to match any application.
* Up to 256 MB memory and internal disk capacity up to 7.2 GB, expandable to greater than 72 GB using additional enclosures.
* High performance I/O subsystem includes four VME expansion slots, Ethernet and two SCSI channels with disk striping support.
* Seven graphics configurations:

* S, no display, server only
* Entry (LG1/2 board) with VME adaptor*
* Express with VME adaptor*
* ELAN with VME adaptor*
* "Clover2": GTX and GTX(B) boardset
* "Powervision": VGX and VGXT boardset
* "Venice": RealityEngine boardset

&lt;nowiki&gt;*&lt;/nowiki&gt;These boards are identical to the IRIS Indigo

=== Notes ===
The memory modules used in the Crimson are the same as on the MC2 memory board used by the Power Series. However, unlike other IRIS 4D series machines an MC2 board is not recognized by the system. All memory (up to 256MB) must be installed on the IP17 mainboard.

The minimal system configuration consists of two cards: IP17 (CPU mainboard) and IO3B (Input/Output mainboard)

While the MIPS R4000 is a 64-bit processor, the Crimson is only capable of running it in 32-bit mode.

IRIS Crimson can operate with IRIX 6.2, but there are bugs in fx.IP17 in the IRIX 6.2 release. In order to prepare a drive you will either need an earlier version of fx, or you must run fx on another system to partition the drive first.

=== Components ===

==== IP17 ====
The CPU mainboard supports either a 100MHz R4000 or 150MHz R4400 CPU with 1MB L2 memory cache and the memory sub-system.

The bus frequency is half of the core speed, either 50MHz or 75MHz depending on the CPU installed.

The differences between the two versions include the PROM revision and different logic on the board.

The Crimson does not support an MC2 board, any memory up to the maximum amount of 256MB must be installed on the IP17 board.

The Crimson supports only one IP17 board unlike its successor, the rackmount Onyx, which supports multiple CPU boards depending on configuration (the deskside Onyx only supports one CPU mainboard but with multiple processors)

==== I03B ====
The Input/Output mainboard supports the following:

* 2 SCSI channels driven with Western Digital 33C93--one internal device connection and one external device connection
* 2 Centronics connectors on the chassis
* 4 serial ports
* 1 parallel port
* 1 AUI 10Mb ethernet port
* 3 powered peripheral ports (8 Pin DIN)

==== Graphics Subsystems ====
The Crimson could be outfitted with seven different graphics setups depending on the end-user's desired needs. Users seeking a file server could opt for no graphics option, which would mean relying on a terminal or network connection to manage the system as there is no basic graphics capability built into the IP17 or IO3B boards. The six other options consisted of varying levels of performance, ranging from Entry graphics, all the way to RealityEngine. These graphics systems were independent of the IP17 and IO3B boards and could be swapped out in order to provide more or less capability as required.

=== Y2k Bug ===
As the IRIS Crimson had already been replaced by the Onyx and Onyx2 prior to the year 2000, little to no work was done to patch the system prior to the turn of the millennium. While the Crimson is not Y2K proof, the error it encounters is not fatal and can easily be rectified by adding a daemon to startup that will sync the time via NTP and reset the Crimson's internal clock. Failure to re-sync the time will cause the system to gain at least one year each time it is restarted until it reaches the end of the Unix epoch at which time it will cycle back. This has the potential for corrupting files and causing licenses to expire prematurely.
[[File:Crimson-jurassic-classic.jpg|thumb|A "Jurassic Classic" Crimson]]

=== In Popular Culture ===
An IRIS Crimson appeared in the main operations center of Jurassic Park. During one scene in the film, the granddaughter of the park's creator, Lex, used the machine to navigate the filesystem of IRIX 4.0 using the application FSN in order to reactivate the locks on the operations center doors. The increase in popularity of the Crimson following the release of the movie prompted Silicon Graphics to release a special edition model referred to as the "Jurassic Classic." It was notable for being marked as such on the outside of the case, in addition to being signed by Silicon Graphics founder Jim Clark.

[[Category:Hardware]]</text>
    <sha1>42c3cd85e89831cfe23e2ec5ba075dcee21e723f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Indy</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>179</id>
    <parentid>145</parentid>
    <timestamp>2025-02-16T21:32:16Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7102" xml:space="preserve">[[File:Indymag.jpg|thumb|500x500px|SGI Indy owned by CB_HK]]
The Indy, code-named "Guinness", is one of the low-end workstations by Silicon Graphics. Selling for around $5000 USD at base price it was one of the cheaper models. It is notable for its common-ness, comparable to the Amiga 500 for Amigas, and its use in development for the Nintendo 64. It was introduced on July 12, 1993 to replace the low end models of the [[IRIS Indigo]] and discontinued on June 30, 1997.

=== Features ===
The Indy is a small desktop (dimensions 41 x 36 x 8 centimetres) computer consisting of a steel frame with a removable bright blue plastic skin. The system is capable of supporting the weight of a small CRT or a modern LCD/LED monitor without damage.

After removing the plastic skin, the power supply, long, thin and bolted to the side of the computer is visible, along with the motherboard, any 3.5" hard disks or the optional Floptical drive, along with the GIO riser and video card, as well as both expansion ports.

==== CPU ====
The processors are supplied on a "Processor Module" board with or without external cache (Primary Cache means no external cache, Secondary Cache means there is an external cache) and range from a 100MHz R4000 to a 180MHz R5000.

Indy's motherboard has a socket for the Processor Module (PM). Early Indys used the 100 MHz MIPS R4000 CPU, which quickly proved inadequate. The Indy, at the bottom of SGI's price list, thus became the primary platform for MIPS's low-cost, low-power-consumption R4600 CPU series. The R4600 had impressive integer performance, but had poor floating-point capability. This, however, wasn't too huge of a problem in a box that was generally not designed for floating-point-intensive applications. For this reason, the R4600 made an appearance outside the Indy line just once, and only briefly, in the Indigo 2. This series of CPU issues, along with the relatively low-powered graphics boards, lower maximum RAM amount, and relative lack of internal expansion ability compared to the Indigo led to the Indy being pejoratively described amongst industry insiders as "An Indigo without the 'go'."

The R4600 chip itself has no L2 cache controller, external controller was used to add 512K of L2 cache. R4600s processor modules both with an L2 cache (SC) and without (PC) are common in the Indy. At the same clock rate, the SC version of the processor module is generally 20 to 40 percent faster than the PC version, due to the memory cache.

The Indy was also the first SGI to utilize the MIPS R5000 CPU, which offered significant advantages over the R4400 and R4600 it replaced. The Indy's 180 MHz R5000 module can be overclocked to 200 MHz by replacing its crystal oscillator chip.

==== Memory ====
The system takes standard 72-pin SIMMS (gold plated SIMMS are recommended to avoid dielectric corrosion) and can take anywhere from as low as 16MB to 256MB, these must be added in sets of 4 at a time since the computer is 64-bits and each SIMM is a 16-bit module.Upon release, the base configuration came at 16MB. IRIX 5.1, the first Operating System for the Indy, did not take full advantage of the hardware due to inadequate memory management and the 16MB configuration failed to even boot. SGI quickly increased the base specification to 32 MB, and shipped free memory upgrades at considerable cost. Subsequent IRIX releases made huge improvements in memory usage.

==== Graphics ====
Graphics are one of three possible types: 8-bit XL, 24-bit XL, and XZ. The 24-bit XL card is the most desirable for collectors due to its decent 2D performance and better than the XZ 3D performance when combined with an R5000 CPU. All three options use the 13W3 connector and require a Sync on Green monitor.

The Indy includes analog and digital video inputs, such as Composite and S-Video, as well as a proprietary digital D-sub used by the Indycam. The system is capable of capturing video at a maximum resolution of either 480i or 576i, depending on region.

It takes a fast machine to capture at either of these resolutions, though; an Indy with slower R4600PC CPU, for example, may require the input resolution to be reduced before storage or processing. However, the Vino hardware is capable of DMAing video fields directly into the framebuffer with minimal CPU overhead.

None of the Indys support video output by default - that would require the Indy Video GIO32 card. In addition, there is an optional video module called CosmoCompress, which offers realtime JPEG video compression and decompression and uses up another GIO32 slot.

==== Networking ====
For networking, the Indy has an on-board AUI, an ISDN port, and a 10Mb Ethernet jack. The AUI and Ethernet cannot be used at the same time, the Ethernet jack takes priority automatically. 10/100Mb cards are available on the used market for faster connection speeds.

==== Storage ====
The Indy has two drive bays for 1-inch tall 3.5" drives. The upper drive bay is externally accessible and may hold a SCSI floptical drive. All external and internal drives share a single Fast SCSI bus (unless a GIO32 SCSI card has been installed). External CD-ROM drive connect via SCSI connector at rear side of the box. Typical drive supports boot, OS install, audio. Special ROM is required to boot from for certain device types.

=== Operating System Support ===
The Indy's basic support came in IRIX 5.1 but that is not a recommended release. The Indy is supported through IRIX 6.5.22, it is recommended to use one of the following releases:

* IRIX 5.3
* IRIX 6.2
* IRIX 6.5.22

IRIX 6.5.22 has the most software available, but will be slow on systems below 128MB. 6.2 and 5.3 are much lighter weight, but have their own limitations.

=== Hardware Problems ===
The component of the Indy most prone to failure is the power supply. Neither the Sony nor the Nidec varieties are more reliable, and both have benefits and drawbacks.

==== MAC/System Serial ====
The Indy's Ethernet address, which doubles as the system's serial number, is stored in battery-backed RAM. This means that when the internal battery dies, so does the system - it will hang at the PROM monitor and refuse to boot any further as a result of the Ethernet address being all FFs. A non-amateur user can replace the PROM battery and reprogramme it. The original battery was made by Dallas Semiconductor, now owned by MAXIM. The original unit was marked the "DS-1386-8K-150", however its replacement unit, the "DS-1386-8K-120" can be directly substituted with no ill effects.

To reset the MAC, it's necessary to use fill commands:

To set the MAC 08:00:69:08:e2:0a, for example, this would be done from the PROM:&lt;pre&gt;
fill -w -v 0x08 0xbfbe04e8

fill -w -v 0x00 0xbfbe04ec

fill -w -v 0x69 0xbfbe04f0

fill -w -v 0x08 0xbfbe04f4

fill -w -v 0xe2 0xbfbe04f8

fill -w -v 0x0a 0xbfbe04fc
&lt;/pre&gt;The MAC address is (usually) on a sticker to the rear of the unit, and hence can be reprogrammed without losing software licenses, which often rely on it to verify ownership. Otherwise, any MAC address in SGI's block is usable.

[[Category:Hardware]]</text>
    <sha1>4c3257805e2521296a822cd77c002e7e740cfaa5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Indigo2</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>180</id>
    <parentid>146</parentid>
    <timestamp>2025-02-16T21:32:49Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4544" xml:space="preserve">The Indigo 2, codenamed "Fullhouse" is a high end workstation marketed by Silicon Graphics from 1993 to 1997, with production of IMPACT models ending in 1998. The Indigo 2 succeeded the earlier [[IRIS Indigo]]&lt;nowiki/&gt;line and is the higher end version of the [[Indy]].

=== Features ===
The Indigo 2 is a large teal or purple desktop that is deceptively heavy, around 40lbs. It came with two plastic feet which can be used to set it upright vertically.

==== CPU ====
The Indigo 2 has three distinct variants, each with a specific motherboard and "IP" number or designation:

* IP22 supports an R4000, R4400, or R4600 CPU clocked at 100-250MHz
* IP26 supports the R8000 CPU clocked at 75MHz
* IP28 supports the R10000 CPU clocked at either 175 or 195MHz

IP26 systems were generally referred to as the POWER Indigo 2, while the IP28 systems usually had a grill badge that read "10000."
[[File:Indigo2-purple.jpg|left|thumb|Indigo2 Impact with an R10000]]

==== Memory ====
All three variants had 12 SIMM slots on the motherboard, organized into three banks of four slots each, and took industry standard fast page mode (FPM) 72 pin SIMMs with parity. Speeds should be 60 or 70 nanoseconds, and the internal organization must be 36 bits wide - 8MB x 72 bit parts will not work.

IP22 systems will support up to 384MB with 32MB SIMMs. While the IP26 and IP28 systems both support 64MB SIMMs, published limits for these systems reflected concerns about the amount of heat generated by then-current DRAM chips. According to SGI the R8000-based IP26 systems would only support 640MB (2 banks of 256MB, one of 128MB), while the R10000-based IP28 would support 768MB (3 x 256MB).

Eventually 64MB SIMMs became available that generated less heat, and denser 128MB SIMMs became available. Both the IP26 and IP28 can use these 128MB SIMMs, but with limitations. IP26 systems require some banks to use lower-profile SIMMs to clear the CPU carrier, and SGI described limits on the mix of different density SIMMs in these systems. However owners have reported working configurations of up to 896MB (1 x 128MB, 1 x 256MB, 1 x 512MB bank).

With the IP28 it is possible to achieve a total of 1GB of RAM (2 banks x 512MB, or 2 x 256MB + 1 x 512MB), but unfortunately this appears to be a hard limit based on address logic.

==== Graphics ====
The graphics boards available for the Indigo 2 were the pre-IMPACT Newport and Express boards (which included the SGI XL24, SGI XZ, SGI Elan and SGI Extreme) and the MGRAS IMPACT boards (the SGI Solid IMPACT, the SGI High IMPACT, the SGI High IMPACT AA, and the SGI Maximum IMPACT). IMPACT graphics is not supported by the Power Indigo 2 (R8000 CPU). The Indigo2's replacement, the SGI Octane, offered an upgraded bus but featured the same graphics options, albeit in repackaged form.

The IMPACT units are purple, though it is feasible to upgrade a teal Indigo 2 with proper upgrade parts.An IMPACT-ready Indigo 2 must have an IMPACT-ready riser card, an IMPACT-ready power supply, and a sufficiently recent PROM revision.

==== Networking ====
For networking, the Indigo 2 has an on-board AUI and a 10Mb Ethernet jack. The AUI and Ethernet cannot be used at the same time, the Ethernet jack takes priority automatically. 10/100Mb cards are available on the used market for faster connection speeds. This is near identical to the Indy's configuration.

==== Storage ====
The internal drive bays of the Indigo2 take model-specific carriers. These carriers mate to a backplane using a non-standard connector, and contain devices using a standard 50 pin IDC ribbon cable connector. There may not be enough room in the carrier to use an adapter board to use 68 or 80 pin devices unless using a down-sized device, e.g. a 2.5" hard drive in a 3.5" drive carrier.

=== Operating System Support ===
The first Indigo 2 systems were introduced during the 4D1-4.x era. These were based on the R4000 microprocessor and featured Express graphics (Elan, XZ). Support for new hardware was added in future releases during this period and later on in the 4D1-5.x era.

Major milestones include the introduction of the Impact graphics options as well as the step from the R4000 to the R10000 CPU. For Impact graphics special versions of the IRIX 5.3 and IRIX 6.2 release were offered. Similarly a special release of IRIX 6.2 was made for the R10000 CPU upgrade.

General support for all Indigo 2 variants can be found in the all platform IRIX 6.5. The support for the remaining legacy systems like the Indigo 2

[[Category:Hardware]]</text>
    <sha1>4d0ba4f974159460bf95433e6c4dad21c51a9aff</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Onyx</title>
  <ns>0</ns>
  <id>53</id>
  <revision>
    <id>181</id>
    <parentid>147</parentid>
    <timestamp>2025-02-16T21:33:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="45600" xml:space="preserve">[[File:Onyx2 with Multichannel.jpg|thumb|Multichannel Display option for an Onyx]]
The Silicon Graphics Onyx (frequently known as the Onyx1 or Original Onyx, or by its form-factor specific codenames Eveready and Terminator) is a graphics supercomputer introduced by Silicon Graphics in 1993 to replace their short-lived [[Crimson]]. Also based on the POWERpath-2 Everest architecture, the Onyx is closely related to the Challenge L/XL systems offered by SGI during the same time period, and shares many parts. In general, the difference between an Onyx and a Challenge L/XL is that while the Challenge usually supports more CPUs and memory (with the exception of the Challenge DM), it does not support the installation of a graphics boardset (with the exception of the Challenge GR). The Onyx sat at the high-end of SGI's early-to-mid 1990s product line, above both the Indigo2 and Indy, and was used for tasks such as visualization, simulation, and early virtual reality systems. The system was succeeded on October 7th, 1996 with the launch of the [[Onyx2]]. Though production of new Onyxes ended in March of 1999, with the end of service in December of 2008, SGI continued to use the Onyx brand name on their most capable graphics systems until July of 2003, with the introduction of the Onyx4. 

=== Variants and Naming ===
The Onyx is a highly modular system, and was offered in a number of processor and graphics combinations throughout its lifespan. Though some configurations (such as an R8000-based Onyx with VTX graphics) were not offered officially, most CPU/Graphics combinations were, each under a different name. There were ten different, individually named "major variants" of the Onyx. The table below describes these.
{| class="wikitable"
| colspan="6" |Table of officially-offered Onyx Variants
|-
|Variant Name
| colspan="5" |Meaning
|-
|Onyx RealityEngine2
| colspan="5" |An R4000-based Onyx using a RealityEngine2 graphics subsystem
|-
|Onyx VTX
| colspan="5" |An R4000-based Onyx using a VTX graphics subsystem
|-
|Onyx Extreme
| colspan="5" |An R4000-based Onyx using an Extreme Graphics graphics subsystem
|-
|POWER Onyx RealityEngine2
| colspan="5" |An R8000-based Onyx using a RealityEngine2 graphics subsystem
|-
|POWER Onyx Extreme
| colspan="5" |An R8000-based Onyx using an Extreme Graphics graphics subsystem
|-
|Onyx InfiniteReality
| colspan="5" |An R4000-based Onyx using an InfiniteReality graphics subsystem
|-
|Onyx 10000 RealityEngine2
| colspan="5" |An R10000-based Onyx using a RealityEngine2 graphics subsystem
|-
|Onyx 10000 InfiniteReality
| colspan="5" |An R10000-based Onyx using an InfiniteReality graphics subsystem
|-
|Reality Station
| colspan="5" |An R4000 or R10000-based Onyx using a RealityEngine2 graphics subsystem. Limited to only one CPU
|-
|i-Station
| colspan="5" |An R4000 or R10000-based Onyx using an InfiniteReality graphics subsystem. Limited to only one CPU
|-
| colspan="6" |Note: SGI does not appear to have officially offered a POWER Onyx VTX, an Onyx 10000 VTX, or an Onyx 10000 Extreme.
|}
SGI Workstation/Client Periodic Table November 4th, 1994 demonstrates the naming discrepancy between Onyx and POWER Onyx systems with Extreme Graphics installed. While POWER Onyxes are labeled with a slash as POWER Onyx/Extreme, Onyxes are labeled without the slash.
[[File:Onyx-R10k.jpg|left|thumb|R10000 Onyx variant]]
In some cases, such as on their Periodic Tables, SGI also listed the number of processors after the first portion (the one which represents the CPU) of the name. For example, a system with RealityEngine2 graphics and four R4000 CPUs would be an Onyx/4 RealityEngine2, a system with RealityEngine2 graphics and twelve R8000 CPUs is a POWER Onyx/12 RealityEngine2 and so-on. Interestingly, R4000 systems with Extreme graphics do not use the "slash-CPU" notation, meaning that, for example, an system with two R4000s and a system with four R4000s, each with Extreme Graphics, are both known simply as the Onyx Extreme. The same goes for the R8000-based POWER Onyx, except that the slash is kept with only the number removed. All R8000-based Onyxes using Extreme Graphics are known simply as the POWER Onyx/Extreme. This strange phenomenon can be seen on the November 4th, 1994 Workstation/Client Periodic Table (image on right) and the very similar Workstation/Client Periodic Table rev. 2/14/95 (the only difference of which is a change to the aesthetic of the title and the removal of the Crimson RealityEngine and its replacement with the Reality Station, which is, redundantly, known there as the Reality Station RealityEngine2). While this discrepancy between the POWER Onyx and the regular, R4000 Onyx's naming schemes could be mistaken for a typo, its presence on two similar but different revisions of the Periodic Table makes this unlikely.

=== Architecture ===
[[File:940110-Periodic Table.jpg|thumb|SGI Periodic Table]]
The architecture of the SGI Onyx can be roughly divided into two main parts — the POWERpath-2 bus (frequently known as EBus) and the HIO bus (also known as IBus), including the buses and interfaces which interface with the system via it. While the POWERpath-2 bus provides a high-speed interconnect for CPUs, memory, and the I/O subsystem, the HIO bus provides both direct expansion capabilities using the HIO connectors on the IO4, and interfaces to a number of other system components over FCI (via the F Controller ASICs), VMEbus (via the FCI-connected VMECC), SCSI (via the S1IC) and numerous miscellaneous interfaces (via the EPC).
[[File:Onyx RE2.png|left|thumb|Onyx2 RealityEngine2 diagram]]
POWERpath-2 is the successor to SGI's POWERpath architecture, which they had previously used in their PowerSeries and Crimson systems. While it is officially known as POWERpath-2, it is often called EBus, short for "Everest Bus", Everest being the codename for the system architecture shared by the Onyx and Challenge L/XL. While not the "true" name of the bus, the "EBus" moniker is frequently used both by Onyx owners and by SGI themselves (such as on the slot number label affixed below the slots of the Onyx cardcage). The 256-bit POWERpath-2 bus has a data transfer rate of 1.2GB/s (as compared to the 64MB/s of the original POWERpath), and is used exclusively for the system's core components, the IP19/21/25, MC3, and IO4 boards (not for add-on options or graphics boards). POWERpath-2 is unique to Everest systems (Onyx and Challenge L/XL), and was replaced with the S2MP architecture in the later Onyx2 and Origin2000.
[[File:Onyx Infinite Reality Diagram.png|thumb|InfiniteReality Onyx Diagram]]
While core components are connected to POWERpath-2, their interface with the rest of the system is provided by the IO4 board. The IO4 uses an internal 64-bit bus, which, like POWERpath-2, has two names, those being HIO and IBus. When referring to add-on cards connected to the IO4 using it, it is usually referred to as the HIO (high-speed I/O) bus. However, it is also used internally on the IO4, and it seems that the term "IBus" is preferred here. IBus has a bandwidth of 320MB/s, and is shared by HIO add-ons, VME devices and the graphics subsystem (via F Controller ASICs and the VCAM), and the IO4's built-in EPC I/O controller (which, in turn, creates another bus used for basic I/O devices, the 16-bit PBus) and S1IC SCSI controller. VME devices and graphics boards do not connect directly to IBus. Instead, the IO4 also contains two F Controller ASICs, each of which connects to IBus and creates an FCI, or Flat Cable Interface. These two FCI interfaces are exposed on two connectors towards the rear of the IO4. Attached to these connectors (resting on standoffs above the IO4's PCB, much like the HIO options in front of it) is another board known as the VCAM, or VME Channel Adapter Module. The VCAM serves two primary functions, each using one of the FCI interfaces created on the IO4.

As the name of the device states, one of these functions is to act as an adapter between the system and its VME add-on boards. VMEbus is an industry-standard bus developed by Motorola for systems based on their 68000 processor, and used in many systems both with and without the 68000. Though the Everest family were the final SGI systems to use VMEbus, it was far from the first, with many previous SGI systems and add-ons also using it. The Onyx implements VME Revision C, as well as the A64 and D64 modes of Revision D, allowing VME bandwidth up to 60MB/s when DMA is used. The deskside Onyx has 4 VME slots, one of which is filled by the VCAM, while the rack has either four or twelve slots, depending on cardcage configuration (see below for details). The VCAM provides this VME interface using its onboard VMEBus controller chip, and interfaces the VME bus to one of its FCI interfaces using the VMECC (VME Cache Controller).

The other FCI interface provided to the VCAM is simply passed through to the backplane, for use by the graphics subsystem. This is the other primary function of the VCAM. The graphics subsystem communicates with the host system over its FCI interface using its GFXCC (meaning unknown, but probably "Graphics Cache Controller", in the vein of "VME Cache Controller").

In an Onyx Rack, the number of VME slots available depends on whether the system's third cardcage is used. When only two cardcages are used, the rack Onyx has four VME slots, all in Cardcage 2, one of which is filled by the VCAM attached to the IO4. This is the same configuration found in deskside systems. When the third cardcage is used, eight more VME slots, for a total of twelve, are made available. These slots are divided into two groups, found in slots 1, 2, 3, 4 and 12, 13, 14, 15 in Cardcage 3. Slots 1 and 12, the first of each group, contain a VCAM-like board known as an RVCAM, or Remote VCAM, which provides a VME bus to the three slots next to it. No RVCAMs are required if only two cardcages are used, as the VCAM connected to the system's IO4 is sufficient to control the VME slots in Cardcage 2.

In systems equipped with Extreme Graphics, the VCAM is replaced with a GCAM (meaning unknown, but likely "GIO Channel Adapter Module", in the vein of "VME Channel Adapter Module"), effectively replacing the system's VME bus with a GIO64 bus (albeit in a strange form factor). While the exact components of the GCAM are unknown, it likely uses an ASIC in order to interface the GIO bus to one of the FCI interfaces usually used by the VCAM. Assuming the naming scheme for FCI-connected devices was followed, this chip was likely known as the GIOCC. An adapter is then used to install an Indigo2 Extreme Graphics option in a "VME" (the actual protocol is GIO, but the same physical slots on the backplane are used) slot. While both the GCAM and the adapter are relatively unknown and extremely rare, the adapter is especially hard to find details about. It has been mentioned only a few times on Nekochan Forums, with user "whiter" referring to it as "the GIO2VME adapter" in one post and "AB5 (GIO64 to 9u VME shoehorn)" in another, and user "thegoldbug" referring to it as "a small circuit board (SLAG2) with resistors that connects to the VME bus", going on to conclude that "The GCAM must be doing all the work". In a thread about this board created by whiter, another user, "kshuff", says that he owns an Onyx with Extreme Graphics, and that it was factory-installed in his system. The board appears to have been named the AB5 (possible meaning Adapter Board 5), though the names GIO2VME and SLAG2 are also possibilities, and is seemingly smaller than a usual VME-like board, while consisting of "resistors". Based on this, it is likely a small board, the electronics of which consist solely of passives, located at the rear of a VME slot and containing a GIO64 connector of the sort seen in the Indigo2. In order to mount the non-VME-sized Extreme Graphics boardset in the Onyx cardcage, as well as to affix it to the adapter board, some form of carrier, likely a simple metal frame, was probably used. How the Extreme Graphics boardset's ports were moved to the expansion panels in the cardcage door or the graphics bulkhead below is unknown. It has been noted that a spare GCAM and AB5 board could be used with an Extreme Graphics boardset from an Indigo2 in order to add graphics capabilities to a Challenge L/XL, however thegoldbug, one of the owners of this hardware mentioned above, claims to have attempted this configuration twice, using two different AB5 boards, unsuccessfully. The possibility of adding a non-Extreme GIO64 board such as an IMPACT graphics boardset or other Indigo2 card to an Everest system using the GCAM and AB5 has also been raised, however the conclusion seems to be that it would not be possible due to driver problems.

==== CPU ====
The Onyx's CPUs reside on the IP board, which is installed in a POWERpath-2 slot. Though there are 22 different CPU boards available for the Onyx, they are divided into three main categories by their IP number. While most SGI systems spanning multiple processor families use only one IP number (such as the O2, which is an IP32 system regardless of whether an R10000 or R5000 is installed), the IP number of the Onyx and its CPU board(s) is determined by its CPU family. The IP19 board contains one, two, or four R4400 (R4000-family) processors, and was originally the only processor board offered in Onyx systems. With the introduction of the POWER Onyx and the R8000, the IP21 board, containing either one or two R8000s, was released. Note that because there is no IP21 board with four processors, the usual maximum processor count of 4 in desksides and 24 in racks is halved to 2 and 12, respectively. Finally, with the introduction of the Onyx 10000, the R10000-based IP25 board was introduced, which, like the IP19 board, can contain one, two, or four processors.

Desksides allow one IP CPU board, which must be installed in its designated slot (labeled on the sticker below the cardcage). Given the maximum of four CPUs per board, this means the maximum number of CPUs that can be installed in a deskside system is four. Rack systems are significantly more flexible, having eleven EBus slots, five in Cardcage 1 and six in Cardcage 2. Slot 6 in Cardcage 2 must be filled by the master IO4 board, however the ten remaining slots can be used for either IP CPU boards or MC3 memory boards. Additionally, the five remaining EBus slots in Cardcage 2 (those not filled by the mandatory Master IO4 in Slot 6) may be used for additional IO4 boards, though the five slots in Cardcage 1 cannot. Up to six of these slots may be filled with IP boards, allowing up to 24 CPUs in an Onyx rack system.
{| class="wikitable"
| colspan="7" |Table of Onyx IP CPU Boards
|-
|SGI Part No.
|IP No.
|CPUs
|CPU
|Clock
| colspan="2" |Secondary Cache
|-
| colspan="7" |IP19 (R4000):
|-
|030-0642-xxx
|IP19
|1
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0249-00x
|IP19
|2
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0250-0xx
|IP19
|4
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0525-00x
|IP19
|1
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0374-00x
|IP19
|2
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0375-00x
|IP19
|4
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0720-00x
|IP19
|1
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0652-00x
|IP19
|2
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0653-00x
|IP19
|4
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0806-00x
|IP19
|1
|R4400
|250MHz
| colspan="2" |1MB
|-
|030-0805-00x
|IP19
|2
|R4400
|250MHz
| colspan="2" |4MB
|-
|030-0804-00x
|IP19
|4
|R4400
|250MHz
| colspan="2" |4MB
|-
| colspan="7" |IP21 (R8000):
|-
|030-0636-00x
|IP21
|1
|R8000
|75MHz
| colspan="2" |4MB
|-
|030-0625-00x
|IP21
|2
|R8000
|75MHz
| colspan="2" |4MB
|-
|030-0751-00x
|IP21
|1
|R8000
|90MHz
| colspan="2" |4MB
|-
|030-0702-00x
|IP21
|2
|R8000
|90MHz
| colspan="2" |4MB
|-
| colspan="7" |IP25 (R10000):
|-
|013-1672-00x
|IP25
|1
|R10000
|195MHz
| colspan="2" |1MB
|-
|013-1675-00x
|IP25
|1
|R10000
|195MHz
| colspan="2" |2MB
|-
|030-1107-xxx
|IP25
|2
|R10000
|195MHz
| colspan="2" |1MB or 2MB
|-
|030-1107-xxx
|IP25
|4
|R10000
|195MHz
| colspan="2" |1MB or 2MB
|-
|030-1673-00x
|IP25
|4
|R10000
|195MHz
| colspan="2" |2MB
|-
|030-1673-101
|IP25
|4
|R10000
|195MHz
| colspan="2" |2MB
|-
| colspan="7" |Note: The 030-1673-101 board is unable to load IRIX 6.2, due to its use of CPU Version 3.1. 6.5.x must be used.
|}
The secondary cache of the IP19 board is installed on SIMM modules, though these are not the same ones found in the MC3's slots. These are available in capacities of 256KB and 1MB. The 1MB SIMM is not only four times larger in terms of capacity, but also has a slightly reduced latency.
{| class="wikitable"
| colspan="7" |Table of Onyx IP19 secondary cache SIMMs
|-
|SGI Part No.
|Capacity
|Latency
| colspan="4" |Color Code
|-
|030-0324-00x
|256KB
|10ns
| colspan="4" |Blue Stripe
|-
|030-0660-00x
|1MB
|8ns
| colspan="4" |Yellow Stripe
|}

==== Memory ====
Memory is installed in the Onyx using one or more MC3 boards. A deskside system can take one MC3 board, while a rack can take up to 8. Note that this means that it is impossible for an Onyx rack to have both the maximum CPU configuration and the maximum RAM configuration, as there are simply not enough EBus slots for 8 MC3s and 6 IP boards, let alone any IO4 boards. The MC3 board has 32 slots, each of which can accept a single SIMM of special ECC-protected memory. Three different models of memory SIMM exist, in capacities of 16 and 64 megabytes (with the 64MB version existing in two different variants). The following is a list of MC3 board revisions. It is believed that all revisions should be interchangeable with no effect on compatibility with other parts. However, this has not been exhaustively tested, and as such it is recommended to leave a working system's MC3 board in place when possible, as all MC3 revisions are essentially equivalent in functionality.

List of Onyx MC3 Memory Board Revisions (by SGI Part Number)030-0245-00x

* 030-0604-xxx
* 030-0607-001
* 030-0613-xxx
* 030-0614-xxx
* 030-0614-106

The following is a table of available Onyx memory SIMMs, to be installed on the MC3.
{| class="wikitable"
| colspan="7" |Table of Onyx MC3 Memory SIMMs
|-
|SGI Part No.
|Capacity
|Latency
|Color Code
| colspan="3" |Construction
|-
| colspan="7" |16MB:
|-
|030-0256-00x
|16MB
|60ns
|Pink Stripe
| colspan="3" |Single PCB
|-
| colspan="7" |64MB:
|-
|030-0257-001
|64MB
|60ns
|Purple Stripe
| colspan="3" |Dual-PCB ("Sandwich")
|-
|030-0257-002
|64MB
|60ns
|Purple Stripe
| colspan="3" |Single PCB
|}

==== Graphics ====
Throughout its lifespan, the Onyx was available with four different graphics options. Initially released with a choice of RealityEngine2 or VTX, options for Extreme graphics and InfiniteReality were introduced later.

The performance characteristics of these graphics options are provided in the table below, for easy comparison.
{| class="wikitable"
| colspan="7" |Performance Characteristics and Features of Onyx Graphics Options
|-
|
|RealityEngine2
|VTX
|InfiniteReality
| colspan="3" |Extreme
|-
|Anti-aliased vectors/sec
|2.0M
|1.0M
|7.4M
| colspan="3" |?
|-
|Triangle Meshes/sec
|1.6M
|1.1M
|11M
| colspan="3" |?
|-
|T-Mesh Gouraud Z, lit
|1.0M
|813K
|?
| colspan="3" |?
|-
|T-Mesh Textured
|988K
|600K
|?
| colspan="3" |?
|-
|Quad Strips, Gouraud, Z
|988K
|600K
|?
| colspan="3" |?
|-
|Pixel Fill, smooth, Z
|90M (1x RM )
180M (2x RM)
360M (4x RM)
|90M
|224M (1x RM)
~450M (2x RM)
"&gt;800M" (4x RM)
| colspan="3" |?
|-
|Pixel Fill, Textured, AA
|55M (1x RM)
~115M (2x RM)
230M (4x RM)
|Presumably 55M
|194M (1x RM)
~400M (2x RM)
"&gt;750M" (4x RM)
| colspan="3" |?
|-
|Trilinear Interpolations/sec
|40M (1x RM)
80M (2x RM)
160M (4x RM)
|Presumably 40M
|"&gt;200M" (1x RM)
~400M (2x RM)
"&gt;800M" (4x RM)
| colspan="3" |?
|-
|Convolutions 5x5 separable
|20M
|?
|? (SGI says "TBD")
| colspan="3" |?
|-
|Z-Buffer
|32-bit Integer
|32-bit Integer (?)
|24-bit Floating Point
| colspan="3" |?
|-
|Color
|48-bit RGBA
|48-bit RGB
|48-bit RGBA
| colspan="3" |?
|-
|Color Planes
|192
|192
|192
| colspan="3" |?
|-
|Overlay Planes*
|8
|8
|16
| colspan="3" |?
|-
|Underlay Planes*
|8
|8
|None (?)
| colspan="3" |?
|-
|Max Bits-per-pixel
|256 (1x RM)
512 (2x RM)
1024 (4x RM)
|256
|256 (1x RM)
|512(?) (2x RM)
|1024 (4x RM)
|?
|-
|Texture Memory
|4MB (RM4)
16MB (RM5)
|4MB (RM4)
16MB (RM5)
|16MB (RM6-16)
64MB (RM6-64)
| colspan="3" |?
|-
|Framebuffer Size
|40MB (1x RM)
80MB (2x RM)
160MB (4x RM)
|40MB
|80MB (1x RM)
160MB (2x RM)
320MB (4x RM)
| colspan="3" |?
|-
|Display
|VGA to non-interlaced HDTV (32-bit) or 1600x1200 (48-bit)
|VGA to 1280x1024
|VGA to non-interlaced HDTV
| colspan="3" |?
|-
|32-pixel Read (/sec? meaning unclear.)
|28.3M
|21.1M
|?
| colspan="3" |?
|-
|32-pixel Write (/sec? meaning unclear.)
|29.1M
|26.8M
|?
| colspan="3" |?
|}
Note: Overlay and underlay plane specifications are confusingly worded in sources, and should be taken with

a grain of salt. Meaning of "32-pixel" measurements is unknown, and they are provided verbatim, as listed in

the original source (sgistuff.net). Numbers for dual-RM setups may be interpolated from listed single and quad

specifications, marked with ~ when 4-RM measurement is not precisely 4x the 1-RM measurement. BPP of 512

in dual-RM IR setup interpolated from single being 256 and quad being 1024, however an SGI brochure lists

the dual-RM i-Station as 1024. This is believed to be an error. This brochure also lists some InfiniteReality details

as "greater than" a certain measurement (presumably a conservative estimate). This "&gt;SOMETHING" format is

preserved here. Details for Extreme Graphics are unknown at this time, and should be determined and added.

VTX specs marked "Presumably" are taken from an IR/RE2 comparison with no mention of VTX, and are based

on the single-RM RE2 figure (as VTX is architecturally identical, but has only one RM).

A Note on "RM"

The RealityEngine2, VTX, and InfiniteReality graphics options for the Onyx all utilize a board called the RMx, x being a version. In the case of the RealityEngine2 and VTX, this can be either the RM4 or RM5, whereas InfiniteReality uses one of two variants of the RM6 (RM6-16 or RM6-64). While, in most discussions, this board is referred to simply as the "RM", the meaning of the acronym is less clear than one might imagine. It appears that the majority of Onyx owners, as well as, in many cases, SGI themselves (see their website, circa 1994), refer to the board as the "Raster Manager". However, in the technical papers for both the RealityEngine2 and the InfiniteReality, the authors refer to it as the "Raster Memory" board. Because of this, it appears that, within SGI, there was either disagreement or confusion as to what "RM" stood for. While both would make for the "RM" acronym, it is generally accepted that "Raster Manager" makes more sense (as, while the board does contain memory, it also performs a significant amount of processing, rather than simply storing data).

RealityEngine2

RealityEngine2, often known as "RE2", was, at the time of its release, the highest end graphics option for the Onyx. While it was later repurposed as a lower-end counterpart to the new InfiniteReality, it was originally the most powerful option available. The RealityEngine2 is an improved version of the RealityEngine graphics offered in Crimson and PowerSeries systems, the differentiating factor being the replacement of the eight processor GE8 with the twelve processor GE10. Additionally, the need to terminate Raster Manager boards using a special "terminated" RM4T board (an RM4 with resistors installed in a socket on the board) was removed, with termination now being handled by the system's backplane. The RealityEngine2 consists of three types of board, installed in specialized graphics slots on the backplane.
{| class="wikitable"
| colspan="7" |Table of RealityEngine2 Boards
|-
|SGI Part No.
|Board Name
|Connected to Edge Connector?
|Function
| colspan="3" |Notes
|-
|030-0325-00x
|GE10
|No
|Geometry Engine - Perform geometric graphics calculations
| colspan="3" |N/A
|-
|030-0513-00x
|DG2
|Yes
|Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0359-001 RM4
|Yes
|Raster Manager - Generate image data from geometry
| colspan="4" |40MB framebuffer RAM per RM4, 4MB texture RAM regardless of board count.
|-
|030-0360-001
|RM4T
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |Like RM4, but terminated for pre-Onyx systems. Resistors in jumper block must be removed if installed in Onyx.
|-
|030-0347-00x
|RM5
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |40MB framebuffer RAM per RM5, 16MB texture RAM regardless of board count.
|-
|030-0506-00x
|PAB1
|No
|Paddleboard Interface - Connect RealityEngine2 to Sirius Video board
| colspan="3" |Connects to DG2. Not needed if Sirius Video is not installed.
|}
The GE10 board contains 12 Geometry Engines, at the center of each is an Intel I860XP (not to be confused with the similar but mostly unrelated terms "i386", "x86", "i586", and so-on) RISC processor. While the i860 family of processors never saw use as widespread as hoped, they were found in numerous other niche uses at the time, such as the NeXTcube's NeXTdimension color graphics board, as well as computers from Oki, Stardent, Hauppauge, and Olivetti. It also saw use in Intel's iPSC/860 and Paragon series supercomputers. In the RealityEngine2, these i860XP processors are used to perform geometry calculations for graphics. Each one of these chips has a combined ALU plus floating point performance of 100 megaflops, meaning that, multiplied by the Geometry Engines on the board, each containing one processor, the total compute performance of the GE10 board is 1.2 gigaflops. Each i860XP processor is provided with two megabytes of DRAM. The GE10 also houses the command processor, which is used to control the graphics subsystem and to implement the OpenGL graphics language. The output of these twelve individual geometry engines is transmitted on the Triangle Bus, for use by the RM board. Interestingly, the design of the Triangle Bus on the RealityEngine2's GE10 board is identical to that of said Triangle Bus on the original RealityEngine's GE8 board. While the increased load of the GE10's four extra geometry engines does increase utilization of Triangle Bus bandwidth, the bus was designed to support more than twice the bandwidth required by the original RealityEngine, meaning that in theory, it would work even with 16 Geometry Engines. This meant that the Triangle Bus did not need to upgraded or redesigned during the development of the GE10. The GE10 board does not connect to the edge connector board, and as such installation of a GE10 only requires that the board be inserted into the backplane, like a regular EBus or VME board.

The RM board inputs geometry data from the Triangle Bus, and outputs digital video data to the DG2. The RM board consists of two main types of processor, the Fragment Generator and the Image Engine. Each Raster Manager board consists of five Fragment Generators, with each Fragment Generator driving sixteen Image Engines. While the functionality of the Raster Manager is complex and spans many different tasks (as discussed in the "RealityEngine Graphics" paper, linked below), the basic architecture of the board inputs data from the GE10's triangle bus, before distributing it between five Fragment Generators. The Fragment Generator consists of four ASICs and eight 16 megabit (2 megabyte) DRAM chips, for a total of 16 megabytes per Fragment Generator and 80 megabytes per RM board. The output of the Fragment Generator is then fed into the input of the Image Engine. The RM4 board contains 20 IMP7 Image Engine chips, each of which contains four individual Image Engines. Each one of these IMP7 chips is surrounded by four four megabit (512 kilobyte) DRAM chips, one for each Image Engine inside. The output of these 80 Image Engines is then output to the DG2 board, by way of the edge connector board, which must be installed. The RM4 board provides 40MB of framebuffer memory per board, and adding more RM4 boards can increase this to a total of 160MB (in a four board setup). The RM4 also provides 4MB of texture RAM, though this capacity is not increased by the addition of further RM4 boards. The closely related RM4T is simply an RM4 with some resistors installed in a jumper block towards the rear of the board, for use as a terminated RM4 in a Crimson or PowerSeries system. If installing an RM4T board in an Onyx, these resistors should be removed from the jumper block prior to use, as the Onyx does not require Raster Manager termination. The newer RM5 maintains the same 40MB of framebuffer RAM, but increases texture RAM to 16MB, again not increased when additional boards are installed.

The DG and RM boards must be connected using an edge connector board, installed at the front of the cardcage and connecting all boards below it. The part number of this edge connector is 030-0233-001. This board carries 160 serial, one-bit 50mhz data paths, which together carry the output of the Image Engines to the DG2. In a single-RM system, half of these paths are used, one for each of the 80 Image Engines. In a dual-RM setup, each data path is assigned to a single Image Engine, with all 160 used. In a quad-RM system, these data paths are multiplexed, with each path carrying the output of two Image Engines. This multiplexing is likely the primary reason why a triple-RM system is not possible, as it would require a strange configuration, such as a half-multiplexed, half-direct use of all 160 paths, or some other special-case implementation. With all 160 paths in use, this board provides a bandwidth of 500 megabytes per second.

On the receiving end of the output of the Image Engines is the DG2 board. This board generates the video outputs exposed on the graphics bulkhead's connectors. The data from the Image Engines is first reassembled into what is effectively a digital video signal by ten crossbar ASICs on the DG2, before the image is dithered from 12- to 8-bit color and passed through Digital-to-Analog converters (DACs) for output to the monitor. Like the RM boards, the DG2 board must be connected to the edge connector board. The DG2 board has connectors for the Graphics Bulkhead, which is installed lower in the chassis and connects to it via ribbon cables.

VTX

VTX is a cost-reduced variant of the flagship RealityEngine2 graphics. Architecturally, a VTX subsystem is identical to a RealityEngine2, however it contains half the Geometry Engines and is limited to a single Raster Manager board. While the single RM board and the DG board are identical to those used in a RealityEngine2, VTX replaces the twelve-GE GE10 board with the six-GE GE10V. An SGI Periodic Table from 1993 lists many variants of Onyx in otherwise-identical VTX and RealityEngine2 configurations. This conveniently allows the reader to determine the price of a VTX subsystem relative to a RealityEngine2, as in all cases, systems with VTX graphics cost $40,000 USD less than their RealityEngine2 counterparts. Despite this significant cost saving to the original buyer, it appears that today, at least with regards to systems owned by collectors and those sold on the used market, VTX-powered Onyxes are significantly less common than RealityEngine2 models, perhaps indicating that the lower cost of VTX was not worth the reduced performance to many original buyers. It appears that SGI may have responded to this apparent lack of sales later in the Onyx's life cycle, with late-era Onyx marketing materials usually omitting the option of VTX entirely (though this could also be said to be because of the introduction of the new InfiniteReality graphics subsystem, effectively rendering the once high-end RealityEngine2 the Onyx's budget graphics offering).

InfiniteReality

InfiniteReality is the later of the two flagship graphics options offered for the Onyx. Being the successor to the RealityEngine2, InfiniteReality is the most powerful graphics option available for the Onyx. Like the RealityEngine2 subsystem before it, InfiniteReality consists of three types of board, the GE, DG, and RM. The primary goal of InfiniteReality was to deliver graphics of a quality similar to that of RealityEngine2 at an increased frame rate. A key goal during the development of InfiniteReality's architecture was that it would not only be fully compatible with the Onyx (in addition to the later, higher-bandwidth Onyx2), but that it would be able to utilize most of its performance on both systems. This affected many elements of the boardset's design, from its physical partitioning into GE, RM, and DG boards (so as to fit into the graphics slots in an Onyx), to its use of a display list subsystem with significant architectural changes to that used in the RealityEngine2 (see linked InfiniteReality: A Real-Time Graphics System paper). These architectural changes were necessary to adequately utilize the InfiniteReality in the Onyx, which interfaced with its graphics at a data rate of approximately 200MB/s, in addition to the roughly twice-as-fast Onyx2, which managed 400MB/s.

Like the RealityEngine2, the InfiniteReality uses one GE board, one DG board, and one, two, or four RM boards, connected to the DG via frontplane card-edge connector board. It should be noted that InfiniteReality's RM boards have a greater power consumption than those used in the RealityEngine2, and, as such, only one or two can officially be used in a deskside (while four is limited to a rack). Despite this limitation, it is rumored that, by installing the power boards from a rack system in a deskside, the system could theoretically power four RMs. While it may be possible to provide sufficient power for the additional boards in a deskside, cooling them is still likely to be difficult for the deskside's smaller fans. While a four-RM deskside would certainly be a rare (possibly even unique), powerful, and compact system, those attempting this configuration should exercise extreme caution, understand that they risk severely damaging their system (especially if it seriously overheats), and should understand that this configuration is unsupported and potentially not even possible. Those seeking a reliable, known-good 4-RM InfiniteReality system are advised to look into an Onyx or Onyx2 rack system, where four RMs is an official configuration, and the system already has the necessary cooling and power capacity without any modification.
{| class="wikitable"
| colspan="7" |Table of InfiniteReality Boards
|-
|SGI Part No.
|Board Name
|Connected to Edge Connector?
|Function
| colspan="3" |Notes
|-
|030-0681-003
|GE12-4
|No
|Geometry Engine - Perform geometric graphics calculations
| colspan="3" |"-4" meaningless on Onyx, denotes 4 GEs. Onyx2's GE14 also had a 2 GE "-2" version (in Reality Graphics systems).
|-
|030-0686-004
|DG4-2
|Yes
|Two-channel Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0687-004
|DG4-8
|Yes
|Eight-channel Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0683-004
|RM6-16
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |80MB framebuffer RAM per RM6-16, 16MB texture RAM regardless of board count.
|-
|030-0684-004
|RM6-64
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |80MB framebuffer RAM per RM6-64, 64MB texture RAM regardless of board count.
|-
|030-0506-00x
|PAB2
|No
|Paddleboard Interface - Connect InfiniteReality to Sirius Video board
| colspan="3" |Connects to DG4-2 or DG4-8. Not needed if Sirius Video is not installed.
|}
Like in the RealityEngine2, data moving through the InfiniteReality begins on the GE board. It is accessed from the host system using the Host Interface Processor, which then provides it to the Geometry Distributor. The Geometry Distributor handles distribution of geometry processing workload among the GE board's four Geometry Engines. The Geometry Distributor is capable of distributing data using either a round-robin or least-busy distribution scheme, though least-busy has a slight performance advantage. The Geometry Distributor provides data to the Geometry Engines in the form of commands, each of which contains an identifier assigned by the Geometry Distributor. The Geometry-Raster FIFO buffer later uses these identifiers to reconstruct the order of the commands before they were sent to the Geometry Engines.

Unlike RealityEngine2's twelve Intel i860 XP processors, InfiniteReality uses four custom in-house ASICs. The Geometry Engine chips used by InfiniteReality each contain three cores, meaning that, like it's predecessor's 12 i860 XPs, the InfiniteReality could be said to have twelve processors for geometry (three in each of the four ASICs). However, this analogy should be used with caution. While the RealityEngine2 truly did have 12 Geometry Engines, each three-core InfinteReality ASIC contains only one 2560-word (32-bit words) on-chip memory, shared by all three of its cores. As such, even ignoring the fact that they are no longer on separate chips, the cores that make up an InfiniteReality Geometry Engine are not as independent with regards to memory as the Geometry Engines are on the RealityEngine2 (where each i860 XP has access to 2MB of its own, off-chip DRAM). This single memory for all three cores also allows them to easily share data, if necessary.

At the output of the four Geometry Engines lies the Geometry-Raster FIFO, an SDRAM-based FIFO buffer capable of storing up to 65536 vertices. As stated above, this FIFO is also responsible for properly ordering its data, based on the identifiers assigned by Geometry Distributor.

The data then moves from the GE board to the RM boards, via the Vertex Bus. While the purpose of the Vertex Bus (to carry data between the GE and RM boards) is similar to that of the RealityEngine2's Triangle Bus, it is implemented differently (see paper linked below), resulting in a significant performance improvement. Data sent over the Vertex Bus is broadcast to all Fragment Generators. The InfiniteReality RM board contains a single Fragment Generator and 80 Image Engines. The Fragment Generator is, as was also the case with its predecessor, composed of multiple chips (the SC Scan Converter, TA Texel Address Calculator, eight TM Texture Memory controllers, and four TF Texture Filtering ASICs). Like on the RealityEngine2, data from the GE board is first processed by the Fragment Generator, then by the Image Engines. Because there is only one per RM board, an InfiniteReality RM board's single Fragment Generator uses all 80 of the image engines on the board, unlike on the RealityEngine2, where each of the five Fragment Generators is given 16 of the 80 total Image Engines. The InfiniteReality also continues the trend of combining four individual Image Engines onto a single Image Engine chip, meaning that only 20 Image Engine chips are needed.

Two variants of the Onyx InfiniteReality RM board are available. The RM6-16 has 16MB of Texture RAM (TRAM), while the RM6-64 has 64MB. Each RM board maintains one copy of texture RAM, meaning that, while the amount of physical texture memory in a system increases when additional RM boards are installed, the amount of usable texture memory remains the same, as the memory on the newly-installed RM board(s) is used simply duplicate the data on the existing RM(s). Because each board must retain its own copy of texture RAM, RM6-16 and RM6-64 boards cannot be mixed in a single system (as, having only a quarter the texture memory, an RM6-16 would be unable to store a full copy of the texture memory contents of an RM6-64). Both the RM6-16 and RM6-64 have 80MB of framebuffer RAM per RM board, double the 40MB seen on the RealityEngine2. Unlike TRAM, framebuffer RAM is not duplicated between RM boards, meaning that more RM boards will increase the total amount of framebuffer RAM in the graphics subsystem, up to a maximum of 320MB (with four RM boards).

Like on the RealityEngine2, the output of the RM boards is sent to the DG board via an edge connector board mounted at the front of the cardcage. The edge connector spans the four RMs, connecting to each, and also connects to the DG board, but does not connect to the GE board or any other boards in the cardcage. This edge connector carries 160 serial data paths, the same configuration used in the RealityEngine2, however their use is more flexible on InfiniteReality systems. The RealityEngine2 utilizes one path per Image Engine in one-RM and two-RM configurations, and multiplexes the outputs of each pair of Image Engines onto a single path in a four-RM configuration. This means that, while the video bandwidth of the frontplane is fully utilized in two-RM and four-RM setups, where all 160 paths are driven by at least one Image Engine, single-RM systems utilize only half of the bandwidth, leaving the other 80 paths unused. Though an InfinteReality system also has only 160 paths for its potential 320 Image Engines, it uses them more efficiently in single-RM configurations. While two RMs will assign one path to each of the 160 Image Engines, and four RMs will multiplex the output of 320 Image Engines onto 160 paths, single-RM InfiniteReality systems allow each of the 80 Image Engines to drive two of the 160 data paths on the frontplane, doubling per-Image-Engine bandwidth. Since InfiniteReality systems use all 160 data paths in all configurations, the bandwidth of the InfiniteReality frontplane is a fixed 1200MB/s.

These 160 signals are recieved by four ASICs at the input of the Display Generator board (these ASICs also add the cursor on top of the incoming video). The video is then sent to one of the Display Generator's two or eight (see below) channels. A DG channel is able to resize its video in realtime (e.g. for output as NTSC/PAL video), and can also control the timing of its output. This timing control is the purpose of the Genlock and Swap Ready BNC connectors on the graphics bulkhead, and is discussed in greater depth in the "InfiniteReality: A Real-Time Graphics System" paper linked below. The channel's 12-bit-per-component digital video signal is then passed through 8-bit DACs, which generate the final analog video signal. It should be noted that Channel 1 contains additional hardware, not found on other channels, allowing it to also output composite and S-Video signals.

InfiniteReality's DG4 board is available in two variants. The DG4-2 has two channels, and was the lower-end "standard" option, while the higher-end DG4-8 has eight channels. It should be noted that the DG4-2 PCB has footprints for the components required to provide extra six channels, however, these components are unpopulated. Particularly noticeable are the footprints for the six large BGA chips along the edge of the board, as well as the six QFPs beside them. Towards the middle of the board is a connector for the PAB2 Sirius Video paddleboard, which must be installed if the InfiniteReality boardset is being used alongside a Sirius Video board. The DG4 board has connectors for the Graphics Bulkhead, which is installed lower in the chassis and connects to it via ribbon cables.

Extreme Graphics

Extreme Graphics is the lowest-end graphics option available for the Onyx. It was also available in the Indigo2, where it was the highest-end option until the introduction of IMPACT graphics in 1995. While Extreme Graphics boardsets are relatively common in Indigo2s, they are a rare and largely undocumented option in the Onyx. While it is generally understood that the graphics boardset itself is identical to the one found in an Indigo2, the hardware used to connect it to the Onyx (which does not normally have GIO64 slots) is poorly documented. Further information about the adapters required for this configuration can be found in the "Architecture" section above. The graphics hardware itself is simply a regular Extreme Graphics boardset (see Indigo2). This configuration is rare, and this, combined with the fact that it is rarely mentioned in official SGI documents, is likely the reason for the scarcity of information surrounding it.

==== I/O ====
The IO4 I/O Controller implements the basic I/O functions for Onyx systems:

* Ethernet Controller
* two fast/wide 16 bit SCSI-2 controllers
* four serial ports (3x RS232, 1x RS422)
* a parallel port
* two Flat Cable Interfaces (for VME or Graphics)

In Onyx Deskside systems 1 IO4 controller can be installed, in rackmount Onyxes up to 6 of these boards can be installed.

=== Operating System Support ===
It is recommended to run IRIX 6.5.22 on all revisions/versions of this machine.

=== Troubleshooting ===
No power-on

If a previously working Onyx with no known power supply issues suddenly refuses to power on (specifically no DC GOOD light, no front panel controller functioning) it is possible the Dallas chip located on the System Controller Board (rear access panel of the Onyx) has gone bad. Replacing the Dallas DS12887 with a new production version will allow the system to power on correctly.

=== Links ===

* "RealityEngine Graphics" paper: &lt;nowiki&gt;http://www.sgistuff.net/hardware/graphics/documents/K.Akeley-RealityEngine.pdf&lt;/nowiki&gt;
* "InfiniteReality: A Real-Time Graphics System" paper: &lt;nowiki&gt;http://people.csail.mit.edu/ericchan/bib/pdf/p293-montrym.pdf&lt;/nowiki&gt;

[[Category:Hardware]]</text>
    <sha1>9faa09942ce46596bd8d093faab54f32bdfd7dd4</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Onyx2</title>
  <ns>0</ns>
  <id>93</id>
  <revision>
    <id>182</id>
    <parentid>148</parentid>
    <timestamp>2025-02-16T21:33:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6584" xml:space="preserve">[[File:Onyx2 Late Logo.jpg|thumb|An onyx2 with the later font]]
For the rack variant, see the [[Origin 2000]] article

The SGI Onyx2, code name ''Kego'', is the successor of the SGI [[Onyx]]. The Onyx2's basic system architecture is based on the Origin 2000, but the midplane and some parts such as the IO6 are different between models. The Onyx2 is notable for the InfiniteReality2, 2E and 3 boards it usually is equipped with, as well as its imposing size, weight and aesthetics.

=== Features ===
The Onyx2 deskside form factor can handle up to 4 CPUs distributed across two nodeboards, a maximum of 4 GB of RAM, one GE-16-4, a single DG5-8 for up to 8 displays, and two IR3 or IR4 raster managers for a maximum of 512 MB and 2 GB respectively of texture memory, and can support up to two users simultaneously out of the box. Possibly more with a CADDUO card installed.

A 3-slot PCI cage can be installed as well as a maximum of 10 XIO cards, giving a massive amount of expandability. This is in addition to 5 hard disks and one 5.25 option drive.

==== CPU ====
The following table shows the possible CPU configurations.
{| class="wikitable"
|Processor
|Clockspeed
| colspan="4" |Cache
|-
|R10000
|180 MHz
|1MB
| colspan="3" |R10000
|-
|R10000
|195 MHz
|4MB
| colspan="3" |R10000
|-
|R10000
|250 MHz
|4MB
| colspan="3" |R10000
|-
|R12000
|300 MHz
|8MB
| colspan="3" |R12000
|-
|R12000
|350 MHz
|4MB
| colspan="3" |R12000
|-
|R12000
|400 MHz
|8MB
| colspan="3" |R12000
|-
|R14000
|500 MHz
|8MB
| colspan="3" |R12000
|}

==== InfiniteReality ====
The Onyx2 can handle the following revisions of the InfiniteReality:
{| class="wikitable"
|Model
|GE Revision
|Raster Manager
|Display Generator
|Texture RAM (MB)
|Raster RAM (MB)
|-
|InfiniteReality2
|GE14-4
|RM7-16 or RM7-64
|DG5-2 or DG5-8
|16 to 32
|80 to 160
|-
|Reality
|GE14-2
|RM8-16 or RM8-64
|DG5-2 or DG5-8
|16 to 64
|40 to 80
|-
|InfiniteReality2E
|GE16-4
|RM9-64
|DG5-2 or DG5-8
|64 to 128
|80 to 160
|-
|InfiniteReality3
|GE16-4
|RM10-256
|DG5-2 or DG5-8
|256 to 512
|80 to 160
|-
|InfiniteReality4
|GE16-4
|RM11-1024
|DG5-2 or DG5-8
|1,024 to 2048
|2,560 to 5,120
|}
[[File:Onyx2-raion-passionlip.jpg|left|thumb|An Onyx2 owned by Raion with the cube logo. ]]


InfiniteReality2 is how hinv refers to an InfiniteReality that is used in the Onyx2. The InfiniteReality2 however, was still marketed as the InfiniteReality. It is the second implementation of the InfiniteReality architecture, and was introduced in late 1996. It is identical to the InfiniteReality architecturally, but differs mechanically as the Onyx2's Origin 2000-based card cage is different from the Onyx's Challenge-based card cage.

The Reality is a cost-reduced version of the InfiniteReality2 intended to provide similar performance. Instead of using the GE14-4 Geometry Engine board and the RM7-16 or RM7-64 Raster Manager boards, the Reality uses the GE14-2 Geometry Engine board and the RM8-16 or RM8-64 Raster Manager boards. The GE14-2 has two Geometry Engine Processors, instead of four like the other models. The RM8-16 and RM864 has 16 or 64 MB of texture memory respectively and 40 MB of raster memory. The Reality was also limited by the number of Raster Manager boards it could support, one or two. When maximally configured with two RM8-64 Raster Manager boards, the Reality pipeline has 80 MB of raster memory.

The InfiniteReality2E is an upgrade of the InfiniteReality, marketed as the InfiniteReality2, introduced in 1998. It succeeded the InfiniteReality board set and was itself succeeded by the InfiniteReality3 in 2000, but was not discontinued until 10 April 2001.

It improves upon the InfiniteReality by replacing the GE14-4 Geometry Engine board with the GE16-4 Geometry Engine board and the RM7-16 or RM7-64 Raster Manager boards with the RM9-64 Raster Manager board. The new Geometry Engine board operated at 112 MHz, improving geometry and image processing performance. The new Raster Manager board operated at 72 MHz, improving anti-aliased pixel fill performance.

InfiniteReality3 is the next upgrade and one of the most common for the Onyx2 and Onyx3000 on the secondhand market. The only improvement over the previous implementation is replacement of the RM9-64 Raster Manager with the RM10-256 Raster Manager, which has 256 MB of texture memory, four times that of the previous raster manager.

InfiniteReality4 is the ultimate iteration, introduced in 2002. Primarily used on the Onyx3000 and Onyx350 "G-Bricks". The only improvement over the previous implementation is the replacement of the RM10-256 Raster Manager by the RM11-1024 Raster Manager, which has improved performance, 1 GB of texture memory and 2.5 GB of raster memory, four and thirty-two times that of the previous raster manager, respectively.

Below is a performance table offering comparisons:
{| class="wikitable"
|Reality
|5.5
|94 to 188
| colspan="3" |100 to 200
|-
|InfiniteReality2E
|13.1 to 210
|192 to 6,100
| colspan="3" |200 to 6,400
|-
|InfiniteReality3
|13.1 to 210
|5,600
| colspan="3" |6,400
|-
|InfiniteReality4
|13.1 to 210
|10,200
| colspan="3" |6,400
|}
[[File:Onyx2-rear.jpg|thumb|Rear of an Onyx2, minimally configured]]

==== Memory ====
DIMMs are available in sizes of 16, 32, 64 and 256 MB. The memory modules used in the Origin 200 and Origin 2000 / Onyx 2 are of the same type. To support the Origin 2000 distributed shared memory model, the memory modules are proprietary and include directory memory, which contains information on the contents of remote caches for maintaining cache coherency, supporting up to 32 processors. Additional directory memory is required in configurations with more than 32 processors. The additional directory memory is contained on proprietary DIMMs that are inserted into eight DIMM slots set aside for its use.

==== IO6G ====
An IO6G base I/O board is present in every system. It is a XIO card that provides:

* a 10/100BASE-TX Ethernet port
* 2 sets of PS/2 ports
* 4 Serial ports provided by dual UARTs
* 1 internal Fast 20 UltraSCSI single-ended port
* 1 external wide UltraSCSI, singled ended port
* 1 real-time interrupt output for frame sync
* 1 real-time interrupt input (edge triggered)

Also on the card is the Flash PROM, NVRAM and real time clock of the system.

==== PCI ====
The system can utilize PCI with the addition of an Origin 2000 XIO PCI "Shoebox" or individual XTalk PCI adapters inserted in the cage. These are the same sort form factor as Octane units.

=== Operating System Support ===
IRIX Versions from 6.4 to 6.5.30 supported the Onyx2

[[Category:Hardware]]</text>
    <sha1>bf7884c67957bfd91a479686cd960a7914525cc5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Octane</title>
  <ns>0</ns>
  <id>70</id>
  <revision>
    <id>183</id>
    <parentid>150</parentid>
    <timestamp>2025-02-16T21:34:45Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9277" xml:space="preserve">[[File:An Octane2 setup.jpg|thumb|An Octane2 setup]]
The Octane and its later version, the '''Octane2''', code named Speed Racer, is a high end workstation marketed by Silicon Graphics between 1996 and 2004. Replacing the [[Indigo2]], it is an SMP-capable (dual CPU) machine running the MIPS R10000 to R14000 series of processors. The main differences between the Octane2 and the Octane are configuration-related. The Octane 2 has upgraded motherboard, power supply, front plane and graphics options, but it's entirely possible to retrofit these upgrades to a regular Octane, creating the "Octane 1.5" as many have popularly dubbed it. 

=== Features ===
[[File:Octane-new-logo.jpg|left|thumb|An Octane late model with the "sgi" logo]]
The Octane's system-board is designated as IP30. The system is based on SGI's Xtalk (Pronounced Cross-talk) architecture. This means it does not use a system bus; instead it has a router XBOW (Pronounced cross-bow) that connects any two of its ports. One of the ports is used for the processor and memory subsystem, one is available for PCI (actually PCI-64) expansion and four are XIO slots (packet-based high-bandwidth bus, somewhat similar to HyperTransport). This makes it very similar to a single node of the SGI Origin 200 system.

The XIO is here and there bridged to PCI-64, using a chip named BRIDGE. The places where it happens include the system board (for the IOC3 multi-I/O chip, two ISP1040B SCSI controllers and RAD1 audio), MENET cards (four IOC3s) and the PCI cage (used for PCI cards in Octane). ARCS is provided as the boot firmware, similar to all contemporary SGI computer systems.

==== CPU ====
The Octane series has single and dual CPU modules. A second CPU cannot be added to a single CPU module, therefore upgrading to two requires replacing the entire CPU module.

What follows is a table of all known models:
{| class="wikitable"
|Processor
|Cache
|Single (Mhz)
|Dual (Mhz)
|-
|R10000SC
|1MB
|175, 195, 225, 250
|175, 195, 225, 250
|-
|R12000SC
|2MB
|270, 300, 400
|270, 300, 400
|-
|R12000SCA
|2MB
|360, 400
|360, 400
|-
|R14000SCA
|2MB
|550, 600
|550, 600
|}

==== Memory ====
The Octane allows 256 MB to 8 GB of system memory, using proprietary 200-pin DIMMs. There are two system board revisions. The first revision (part number 030-0887-00x, usually distinguished by a black handle) only supports 2GB of RAM while the later one (part number 030-1467-001, with a silver handle) supports up to 8GB. The -0887 revision of the mainboard will work with all 32-128 MB DIMMS and the stacked variant of 256MB DIMMS, but not the later single-board version (SGI P/N 9010036). The memory subsystem has vast reserves of bandwidth that can be directly served by the Xbow router to any XIO card.

The Octane's memory controller is aptly named HEART. It acts as a controller between the processor, the memory (SDRAM) and the XIO bus.

==== Graphics ====
Graphics on the Octane are provided by a series of cards: SI, SI+T, SSI, MXI. These are updated XIO versions of Solid Impact (SI), High Impact (SI+T) and Maximum Impact (MXI) from the SGI Indigo2 that were internally designated by SGI as 'MARDIGRAS'. The boards were accelerated and reengineered with faster geometry engine and texture modules to create their new versions: SE, SE+T, SSE, MXE. The SI/SE provides 13.5MB of framebuffer memory while the SSE and MXE have a 27MB framebuffer. The '+T' indicates an additional high speed RDRAM texture board which gives 4MB of texture memory, which is practically indispensable, though quite expensive and fragile. The SI/SE+T has one texture board while the MXI/MXE has 2 texture boards, however, the 2 boards in the MXI/MXE do not double the available texture memory to the system. It just doubles the texture performance.

Later Octanes and Octane 2s support the SGI VPro graphics board series, designated 'ODYSSEY'. The first VPro series cards were the V6 and V8. The main differentiator being that the V6 has 32MB of RAM (unlike the MARDI GRAS option, framebuffer memory and texture memory come from the same pool) and V8 having 128MB. Later, the V10 (32MB) and V12 (128MB) were introduced. The main difference with the new VPro V10/V12 series is that they had double the geometry performance of the older V6/V8. V6 and V10 can have up to 8MB RAM allocated to textures (2X more than the textured-enabled MARDIGRAS options), while V8 and V12 can have up to 108MB RAM used for textures.

The VPro graphics subsystem consists of an SGI proprietary chip set and associated software. The chip set consists of the buzz ASIC, pixel blaster and jammer (PB&amp;J) ASIC, and associated SDRAM.

The buzz ASIC is a single-chip graphics pipeline. It operates at 251 MHz and contains on-chip SRAM. The buzz ASIC has three interfaces:

* Host (16-bit, 400-MHz peer-to-peer XIO link)
* SDRAM (The SDRAM is 32 MB (V6 or V10) or 128 MB (V8 or V12); the memory bus operates at half the speed of the buzz ASIC.)

* PB&amp;J ASIC

As with the MARDIGRAS boards, all VPro boards support OpenGL in hardware (MARDIGRAS is OpenGL 1.1 + SGI Extensions, while VPro upgraded support to OpenGL 1.2) and OpenGL ARB imaging extensions, allowing for hardware acceleration of numerous imaging operations at real-time rates.

Compatibility: The V6/V8 boards require an XBOW 1.3 board, but the V10/V12 boards do appear to require an XBow 1.4 frontplane.

==== I/O and HEART ====
The Octane supports Ultra Wide SCSI devices and has two SCSI controllers. System can have up to three internal 3.5" SCSI SCA devices. Octanes use special mounting sleds for the hard drives which are compatible with Origin 2000, Origin 200 and Onyx2. The system also has external Ultra Wide SCSI bus.

The aptly named HEART is the core of the Octane. It integrates a SDRAM memory controller, a XIO device, an interrupt controller and a processor bus interface for up to four R10000-class processors.

The HEART can be accessed in two ways from the processor. The first one is through the PIU (Programmed I/O Unit) at 0xFF0000 in processor physical address space. The other one is at widget 8 in XIO address space. The only one way available to other XIO devices is through the widget interface, so the Interrupt Status Set register is mapped there at address 0x80.

The HEART contains a SDRAM memory controller with ECC. ECC errors are signaled to the CPUs by interrupts.

The XIO bridge is one of the main functions of the HEART. There are three access windows defined for each XIO widget number. There is a window at 0x10000000+ W*0x1000000 for widget number W, a window at 0x800000000+W*0x80000000 and a window at 0x1000000000+W*0x1000000000.

Note that XIO accesses are deeply pipelined by default. Due to that fact, writing to any XIO widget may not have any effect for several hundred cycles. To guarantee finalization of all posted writes it is required to read the widget flush register.

The XIO bridge in HEART provides also some Flow Control features for two channels. They allow to schedule a hiwater IRQ for any given XIO register address. If the register is an input to a FIFO, as is the case with the IMPACT graphics board, exceeding a prescribed number of writes to this register would cause a FIFO hiwater condition. As you already know, the XIO writes are posted and not immediately executed. Catching the hiwater condition in the HEART and not in the card allows to trap it in a more reliable way.

The HEART interrupt controller is visible from the PIU as a set of registers: interrupt mask registers for all processors (IMR0:3), an interrupt status register (ISR) and ISR clear and set registers that allow atomic manipulation of the ISR.

The XIO side consists of a single register 0x80 that can accept either an atomic ISR bit set command or an atomic ISR bit clear command. These commands cause asserting and deasserting IP7:2 bits in the CPUs whose IMRs contain the bit in question.

A small part of the HEART is a programmable interval timer, consisting of 24-bit COUNT and COMPARE registers. The IRQ can be delivered only to the IP6 bit, which is the highest-priority CPU interrupt except internal CPU timer and HEART error IRQs. The timer counts at 12.5 MHz, every 8th internal HEART cycle (1/4th of the XIO frequency).
[[File:Octane2.jpg|thumb|Another view of an Octane2]]
The HEART controls also the Number In a Can associated with processor modules. It features a standard SGI issue MicroLAN controller. 

=== Octane 2 Upgrades ===
Octane 2 has a revised power supply, system-board and XBOW. Octane 2 also shipped with VPro graphics and supports all available VPro cards (V6, V8, V10 and V12). Later revision Octanes also included some of the improvements mentioned.

The case is blue instead of the green used by the original, the plastics are compatible between the two and the chassis is identical.

=== Operating System Support ===
The Octane was first supported by IRIX version 6.4 with IMPACT or "Mardi Gras" graphics (SI/SSI/MXI and later Enhanced versions). Support for VPro or "Odyssey" graphics in Octanes was introduced with IRIX 6.5.10 for V6/V8, and in IRIX 6.5.11 for V10/V12. (Drivers were released to support V10/V12 under 6.5.10.) All versions of IRIX through 6.5.30 include support for the Octane family machines.

[[Category:Hardware]]</text>
    <sha1>7bdaa7664164a93e9015aeaf59e460e663e5824e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>O2</title>
  <ns>0</ns>
  <id>74</id>
  <revision>
    <id>184</id>
    <parentid>151</parentid>
    <timestamp>2025-02-16T21:35:12Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9506" xml:space="preserve">The Silicon Graphics O2, codename Moosehead, is an entry-level Unix workstation introduced in 1996 by Silicon Graphics, Inc. (SGI) to replace their earlier [[Indy]]. Like the Indy, the O2 uses a single MIPS microprocessor and was intended to be used mainly for multimedia. Its larger counterpart was the SGI [[Octane]]. The O2 was SGI's last attempt at a low-end workstation.

=== Features ===
O2 features a proprietary high-bandwidth Unified Memory Architecture (UMA) that connects the various system components. The O2 is a highly-integrated system, with CPU, graphics accelerator, memory, SCSI controller, and I/O all incorporated into a single system module, which can be slid out of the chassis with the flip of a lever. A PCI bus is bridged onto the UMA with one expansion slot available. The O2 has a designer case and a modular design, with space for two Ultra SCSI drives mounted on special sleds (only one in the later R10000/R12000 models) and an optional video capture / sound module mounted on the far left side. Further information on the design and construction of the O2 can be found in SGI service manuals on Techpubs. Detailed breakdown pictures and an IRIX hinv dump can be found here.

An O2's unique system ID (MAC address) is stored on the small PCI riser card that connects the PCI card holder to the motherboard. If this riser card is swapped, the corresponding black plastic badge on the rear of the case should be swapped as well to preserve consistency.

WARNING: The O2 system module should NEVER be removed or installed while the power cord is connected. Doing so can permanently damage the motherboard.

==== CPU ====
The O2 comes in two distinct CPU flavours; the low-end MIPS 180 to 350 MHz R5000- or RM7000-based units and the higher-end 150 to 400 MHz R10000- or R12000-based units. The 200 MHz R5000 CPUs with 1 MB L2-cache are generally noticeably faster than the 180 MHz R5000s with only 512 KB cache. There is a hobbyist project that has successfully retrofitted a 600 MHz RM7xxx MIPS processor into the O2.

There is also a hobbyist project that has successfully retrofitted a 600 MHz R7000 MIPS processor into the O2. In theory faster CPUs at 900MHz any beyond are possible, but this would require the public release of the O2 PROM source code which at present is not available and probably never will be.
[[File:O2 full setup.jpg|thumb|An O2 in full setup]]
A recall of some early versions of the RM7000A 350Mhz CPU is thought to have hastened the removal of the O2 from SGI's product line.

==== Memory ====
There are eight DIMM slots on the motherboard and memory on all O2s is expandable to 1 GB using proprietary 239-pin SDRAM DIMMs. The Memory &amp; Rendering Engine (MRE) ASIC contains the memory controller. Memory is accessed via a 133 MHz 144-bit bus, of which 128 bits are for data and the remaining for error-correcting code (ECC). This bus is interfaced by a set of buffers to the 66 MHz 256-bit memory system.

Original SGI-branded O2 DIMMs are either single-sided (SS) with memory chips on only one side of the module or double-sided (DS), and are color-coded to assist in identification. 3rd party DIMMs may or may not follow these conventions. Knowing the current memory configuration is important as DIMMs must be installed according to a number of specific rules.

* The DIMMs in slots 1 and 2 make up Bank A. DIMMs in slots 3 and 4 make up Bank B, and so on.
* A bank of two slots must have a DIMM in each slot or be empty (except for slots 1 and 2, Bank A, which must always be populated.)
* The two DIMMs in any bank must be of the same size and type.
* The largest size DIMMs must be in Bank A.
* DIMM banks must be filled sequentially, beginning with bank A.
* Equal or smaller size DIMMs must be in Bank B, and so on.
* Do not skip banks, or the memory will not be recognized.

To install high density (128 MB) DIMMs, PROM revision 4.4 or higher is required. With older PROM revisions maximum memory is 256 MB. For IRIX 6.3 there are patches to upgrade the PROM as described in "Silicon Graphics® O2® Workstation Memory Installation Instructions", for IRIX 6.5 PROM images come with the operating system and overlays CD sets.

==== Graphics ====
[[File:SGI O2.jpg|left|thumb|An early-model O2 with the original cube logo]]
The CRM chipset that SGI developed for the O2 shares OpenGL calculations with the CPU. Due to the unified memory architecture, video memory is shared with main memory, and there is effectively an 'unlimited' amount of texture memory. Another useful feature is that any incoming video data from the Audio/Video option can be mapped directly as an OpenGL texture without having to perform a copy or move.

ICE (Image Compression Engine — a dedicated 64-bit R4000-based processor containing a 128-bit SIMD unit running at 66 MHz, which is used to accelerate various image and video operations)

The O2 Video system supports two simultaneous input video streams and one output video stream which can be separated into two outputs, one carrying pixel information, the other carrying alpha (key) information.

Using the O2 Video system, it is possible to capture live video into the computer's memory which can then be displayed in a graphics window on the screen or further processed by an application. It is also possible to generate video output from images in memory, which can be displayed on a standard video monitor, or recorded to a VTR. Using the VL programming library, a program can capture video in either the RGB or YCrCb color spaces, and either full or reduced size formats, and in a format usable for input to the compressor/decompressor, display on the graphics screen, or as an input to a graphics processing and/or texture operation.

SGI offered two video options for the O2/O2+: the AV1 interface and the AV2 interface.

The AV1 interface supports Composite and S-Video (Y/C) (both analog), and Digital I/O via the Camera/Digital Video port. The analog I/O jacks are for use with standard analog video equipment, supporting both PAL and NTSC video formats. There are a variety of controls available that allow the user or programmer to set various parameters used for the decoding and encoding of the video signals. The digital input of the AV1 is for use with the O2Cam Digital System Camera, or can be connected to an optional digital video input and output adapter to interface to standard SMPTE259M serial digital video devices.

The AV2 interface supports two ITU-601 (CCIR-601) serial digital video input connectors and two similar output connectors, as well as GPI input and output and analog (black burst) sync input and loop through.

==== I/O ====
I/O functionality is provided by the IO Engine ASIC. The ASIC provides a 33-bit PCI-X bus, an ISA bus, two PS/2 ports for keyboard and mouse, and a 10/100 Base-T Ethernet port. The PCI-X bus has one slot, but the ISA bus was present solely for attaching a Super I/O chip to provide serial and parallel ports.

=== O2+ ===
[[File:SGI O2+ by Mattst88.jpg|thumb|An O2+, property of mattst88]]
The O2+ is a special variant of the SGI O2 with a purple/grey color scheme, top of the line multimedia, CPU and memory. It was produced in very low quantities and has remained a valuable item for collectors, selling for many times the going rate for O2s on average.

=== Operating System Support ===
IRIX versions 6.3 and 6.5 (up to the latest overlay - 6.5.30) are supported on this machine, however, only in 32-bit mode, due to the nature of the O2's internal architecture. For CPU-specific versions, see also: IRIX for O2.

Besides the default CD-based Installation, the O2 also supports network installation.

=== Hardware Problems ===
The Toshiba CD-ROM drives in the O2 commonly throw a small white plastic gear from the tray motor. Symptoms include the tray either refusing to open or refusing to stay closed. This problem is relatively easy to fix by opening the CD-ROM drive and pushing the gear back onto the motor shaft, then adding a small amount of glue to keep the gear in place. To avoid damaging the tray mechanism during ordinary use, do not push it closed: use the "inject" command instead.

To quote kjaer in a Nekochan forum post &lt;nowiki&gt;https://web.archive.org/web/20170821000034/http://forums.nekochan.net/viewtopic.php?f=3&amp;t=16726667&lt;/nowiki&gt; "...there is a pressfit nylon pinion on the transport motor that opens and closes the drive tray, and also raises and lowers the optical pickup assembly (moves it closer to the disc after the tray closes, and moves it away from the disk before the tray opens). This pinion splits when it ages, and when this happens the static friction between pinion and spindle is no longer sufficient to hold the torque required to lift the optical pickup. The drive interprets this as a mis-load and ejects the tray." A further discussion with images can be found &lt;nowiki&gt;https://web.archive.org/web/20170820231441/http://forums.nekochan.net/viewtopic.php?f=3&amp;t=16727779#p7360973&lt;/nowiki&gt;

==== Memory ====
The O2's proprietary memory modules are highly susceptible to dirt and shock, particularly during shipping. The symptoms of a bad memory contact include random memory errors and a total inability to boot, with a solid red or blinking amber LED at startup. Careful cleaning and re-seating of memory will typically solve such problems, though the DIMMs should also be carefully inspected for missing surface-mount components, which can be easily knocked-off via mishandling.

[[Category:Hardware]]</text>
    <sha1>5422db26bc781d61c1151ff6d339632c0466dd2d</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Origin 3000</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>185</id>
    <parentid>152</parentid>
    <timestamp>2025-02-16T21:35:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6502" xml:space="preserve">[[File:Origin 3000 Rack Cluster.jpg|thumb|An Origin 3000 Rack cluster]]
The SGI Origin 3000, is the successor of the SGI [[Origin 2000]] line. Unlike previous versions, it did not offer a deskside version, opting for full and half rack configurations instead. It also introduced the "brick" architecture used by many Chimera architecture SGIs.

=== Features ===
Physically, the Origin 3000 is based on "bricks" - rackmounted modules that provide a specific function, that are connected together using NUMAlink 3 cables for modules providing compute functions, or Crosstown2 cables for modules providing I/O functions. These bricks are mounted in a standard 19-inch rack. There are two racks for the Origin 3000, a 17U-high half rack, and a 39U-high tall rack. Architecturally, the Origin 3000 is based on the distributed shared memory NUMAflex architecture. The NUMAlink 3 system interconnect uses a fat tree hypercube network topology.

The following table shows a list of models and their possible configurations:
{| class="wikitable"
|Model
|CPUs
|Memory
|Chassis
|-
|Origin 3200
|2 to 8
|Up to 16 GB
|Half Rack
|-
|Origin 3400
|4 to 32
|Up to 16 GB
|1 Full Rack
|-
|Origin 3800
|16 to 512
|Up to 1 TB
|1-16 Full Racks
|-
|Origin 3900
|4 to 512
|Up to 1 TB
|1 to 4 Full Racks
|}

==== C-Brick ====
[[File:Comparison of the O2k to the O3k.jpg|left|thumb|Comparison of the Origin 2000 and Origin 3000, side-by-side]]
The C-Brick (Compute Brick) is a 3U-high enclosure that contains CPUs on a PCB. The node contains two or four processors, the local and directory memory, and the Bedrock ASIC. The two processors and their secondary caches is contained on a PIMM (Processor Integrated Memory Module) daughter card that plugs into two 240-pin connectors on the node board. Initially, the Origin 3000 used the 360 MHz R12000 and the 400 MHz R12000A processors with 4 or 8 MB of secondary cache. In May 2001, the 500 MHz R14000 was introduced with 8 MB of secondary cache and in February 2002, the 600 MHz R14000A was made available. Near the end of its lifetime, the C-Brick was updated with 800 MHz MIPS processors.

==== CX-Brick ====
[[File:Origin 3000 Full Rack.jpg|thumb|An Origin 3000 Rack]]
The CX-Brick is a 4U-high enclosure that is only used in Origin 3900 and Onyx 3900 systems. It differs from the C-Brick by containing four node boards and eight-port router ASIC. The CX-Brick can support up to 16 processors and 32 GB of memory. The CX-Brick initially used the IP53 motherboard that supported 500 MHz R14000 and 600 MHz R14000A processors with 8 MB secondary caches, later upgraded to use the R16000 and R16000A. It connects to the system using NUMAlink 3.

=== R-Brick ===
The R-Brick (Router Brick) is a 2U-high enclosure that features an eight-port router ASIC. Its purpose is to route NUMAlink packets throughout the system to connect the C-Bricks together. R-bricks for the Origin 3400 have a router ASIC with two ports disabled to prevent them from being upgraded into Origin 3800 systems.

=== I-Brick ===
The I-Brick is a 4U-high enclosure that provides boot I/O functions for the Origin 3000. It features five hot swappable PCI-X slots, with three clocked at 33 MHz and two at 66 MHz on two separate buses, two sled-mounted 3.5-inch Fibre Channel hard drives and a proprietary CD-ROM drive. The I-Brick also provides a 10/100BASE-T Ethernet port, an IEEE-1394 port, a serial port, two USB ports as well as a real time clock and NVRAM for storing configuration information through the IO9. It connects to the system using Crosstown2.

==== IX-Brick ====
The IX-Brick is a 4U-high enclosure that is only used in Origin 3900 and Onyx 3900 systems. It an updated version of the I-brick with 133 MHz PCI-X expansion slots. It connects to the system using Crosstown2 cables.

=== V-Brick ===
The V-brick is a 4U-high enclosure that supports two InfinitePerformance (Commercial name for VPro/Odyssey Graphics) graphics pipes. Each graphics pipe consists of a 128 MB SGI VPro V12 graphics card. The V-brick connects to the system using Crosstown2 cables. This was one of two options for graphics.

=== G-Brick ===
The G-brick is a 18U-high enclosure that supports the InfiniteReality graphics subsystem. Each G-brick can support two InfiniteReality3 or InfiniteReality4 graphics pipes, although only one pipe can have four raster manager boards while the other can have two. The G-brick connects to the system using Crosstown2 cables.

==== Other Bricks ====
[[File:G-Brick.jpg|thumb|An Origin 3000 G-brick]]
Some systems were offered with D, P, PX and X Bricks. D is for data, and contains Fibre Channel, P and PX are PCI-X peripheral bricks, and X is an XIO brick.

=== Memory ===
The C-Brick supports 512 MB to 8 GB of local memory through eight DIMM slots organised into eight banks by using proprietary 100 MHz ECC DDR SDRAM DIMMs with capacities of 256 MB, 512 MB and 1 GB. The data path between the DIMM and the Bedrock ASIC is 144 bits wide, with 128 bits for data and 16 bits for ECC. Because the Origin 3000 uses a distributed shared memory model, directory memory is used to maintain cache coherency between the processors. Unlike the Origin 2000, which requires dedicated proprietary DIMMs for the directory memory, the Origin 3000's directory memory is integrated in the same DIMMs that contain the local memory. Due to this, there are two kinds of DIMM used in the Origin 3000: standard DIMMs, which supports systems with up to 128 processors, and premium DIMMs, which supports systems with more than 128 processors. The 256 MB DIMM is a standard DIMM, the 1 GB DIMM is a premium DIMM and the 512 MB DIMM can be either.

=== Power Supply ===
The Origin 3000 uses a "Power Bay" that contains up to 6 hot swappable powersupplies and provides the Bricks of the system with power (48VDC). It is connected to a wall outlet using a Power Distribution Unit. For this reason, most configurations require 240V. The 3400 and 3800 configurations had alternative setups for power.

=== L2 and L3 Controllers ===
The L2 and L3 Controllers are control systems used to manage the status of each brick in the system and to issue commands, monitor the environment and more. The L2 controller is a small Linux-based silver box that runs Linux on an embedded PowerPC system. The L3 controller was a Linux-based console that could manage several L2 systems.

=== Operating System Support ===
IRIX Versions from 6.5.15 to 6.5.30 supports the Origin 3000.

[[Category:Hardware]]
[[Category:Stubs]]</text>
    <sha1>5732ea64589ec400cd693369d0265d911dbfe368</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>MIPSPro</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>189</id>
    <parentid>5</parentid>
    <timestamp>2025-02-16T21:37:21Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13163" xml:space="preserve">MIPSPro is the IRIX-native C/C++/FORTRAN compiler that was distributed by SGI for use in IRIX development.

This page serves to document MIPSPro's behavior, characteristics, compatibility, and differences from other UNIX-style cc compilers and the GNU Compiler Collection.

For legacy MIPSPro releases and documentation, see [[IRIS Development Option]] for more info.

=== General ===
MIPSPro is not installed in a standard IRIX install and requires a collection of other discs that contain the compiler, development libraries/header files, toolchain and supporting utilities.

MIPSPro supports three ABIs, O32, N32 and N64 (Not to be confused with the Nintendo 64). The O32 ABI is the MIPSII 32-bit ABI, and stands for Old 32. The N32 ABI is analogous to the Intel x32 ABI used on x64 systems to provide enhancements to 32-bit programs through using 32-bit pointers while offering many of the N64 ABI enhancements over O32. The N64 ABI is the native 64-bit ABI for IRIX.

Several compiler front ends were available, including the C, C++ and FORTRAN compilers. Others may have possibly been available at various points historically.

=== Optimization ===
MIPSPro supports -O0,1,2,3, and fast flags, as well as a number of other optimization/architecture flags:

-mips4 will enable the MIPS IV instruction set

-TARG will enable platform or CPU-specific optimizations

-OPT can tune various optimizations

For a full list, please check: &lt;nowiki&gt;https://irix7.com/techpubs/007-2360-006.pdf&lt;/nowiki&gt;

==== TARG flag ====
The TARG flag controls both platform and CPU specific optimizations and will take a variety of commands:

-TARG:proc=R10000 will, combined with the MIPSIV flag, compile for MIPS IV platforms and enable specific optimizations for the R10000 processors. The resulting binary will run on R5000 and R8000 systems, but will skip the optimizations for those platforms.

-TARG:platform=IP30 will, combined with other flags, enable Octane specific optimizations.

The two commands can be combined as so: -TARG:platform=IP30:proc=R10000 as well as other commands.

==== OPT flag ====
This has a number of useful flags for more carefully optimizing code.

-OPT:space Optimizes the program for size, similar to the GCC -Os flag

-OPT:Olimit=n This sets a cutoff limit on procedure sizes to optimize. Procedures above the set size will be left alone. The compiler will normally during compilation throw notices out advising of potential ways to tune this.

-OPT:alias=value The compilers must normally be very conservative in optimization of memory references involving pointers (especially in C), since aliases (that is, different ways of accessing the same memory) may be very hard to detect. This option may be used to specify that the program being compiled avoids aliasing in various ways. See the above document for various applications.

Other flags are listed in the above document

=== C Programming with MIPSPro ===
Much like GCC and other modern compilers, MIPSPro can be called from the commandline like so:

&lt;code&gt;% cc foo.c&lt;/code&gt;

Where foo.c is a presumably simple test file.

MIPSPro's ABI, compiling and configuration is via &lt;code&gt;/etc/compiler.defaults&lt;/code&gt;. This can be overridden with compile-time flags, or ENV variables. SGI_ABI, for instance, controls the active ABI:

&lt;code&gt;% setenv SGI_ABI -n32&lt;/code&gt;

This will set it to -n32 mode.

==== Strictness ====
MIPSPro is far more strict than GCC about accepting standard C code and its compiler infrastructure is entirely different. Common bad programming techniques that work in GCC may not work on MIPSPro, this section aims to document common pitfalls:

=====Variable Attributes=====

These are not supported, so they have to be patched with #ifdef or removed:

&lt;code&gt;__attribute__(( XXX ))&lt;/code&gt;

This is the structure of these.

One variable attribute can be rewritten to work with MIPSPro: the attribute 'packed' for a struct can be enforced in MIPSPro by placing the struct between two pragma blocks:

&lt;pre&gt;#if defined (__sgi)

+#pragma pack(1)

+#endif

struct {

...

};

&lt;nowiki&gt;#&lt;/nowiki&gt;if defined (__sgi)

+#pragma pack(0)
+#endif
&lt;/pre&gt;

=====Zero Length Arrays=====

This is a GNU extension prior to c99. Using c99 or -c99 flag for cc should allow it to work.

=====Variable Length Arrays=====

Only supported using the c99 driver or -c99.

=====String Literals=====

IRIXNet staff Dexter1 helpfully pointed this out in a forum post:

Shorthand initialization of char a[] = " "; with MIPSpro will go wrong with leading zero bytes. Rewrite that code.

What follows is his example copied mostly-verbatim:
&lt;pre&gt;
&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;stdio.h&gt;

&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;stdlib.h&gt;

&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;memory.h&gt;

int main(void) {

const char a[] = "\0This is a text";

const char b[] = { 0x0, 'T', 'h', 'i', 's', ' ', 'i', 's', ' ', 'a',

' ', 't', 'e', 'x', 't', 0x0 };

const char *c = "\0This is a text";

char buf1[128];

char buf2[128];

char buf3[128];

size_t lena = sizeof(a) - 1;

size_t lenb = sizeof(b) - 1;

size_t lenc = 15;

memcpy(buf1,a,lena);

memcpy(buf2,b,lenb);

memcpy(buf3,c,lenc);

printf("length a : %d, length b %d, length c %d\n", lena, lenb, lenc);

printf("buf11 : %x, buf21 : %x, buf31 : %x\n", buf11, buf21, buf31);

printf("comparing a with buf1 : %d \n", memcmp(a,buf1,lena));

printf("comparing b with buf2 : %d \n", memcmp(b,buf2,lenb));

printf("comparing c with buf3 : %d \n", memcmp(c,buf3,lenc));

printf("comparing buf1 with buf2 : %d \n", memcmp(buf1,buf2,lena));

printf("comparing buf1 with buf3 : %d \n", memcmp(buf1,buf3,lenc));

printf("comparing buf2 with buf3 : %d \n", memcmp(buf2,buf3,lenb));

return 0;
}
&lt;/pre&gt;
Consider this code. The three text containers a, b and c are initialized differently but all should contain "This is a text" preceded and suffixed by a zero byte.

* Container a's type is an array of char. Its lifetime is limited to the main scope and its initialized content gets put on the stack by the compiler.
* Container b is the longer version of a and is also typed array of char.
* Container c is a pointer to a read-only memory block of chars allocated and initialized by the compiler on the heap.

If compiled with MIPSpro cc or c99 and ran, it becomes apparent that array a is not initialized properly. a1 should contain capital 'T' but instead it's a zero byte: once looking at the stack where a is put with a debugger, there is nothing: The preceding zero byte interferes with compiler code and the stack, although it will allocate the correct amount of bytes on the stack, will only contain zeroes.

This 'shorthand' initialization of an array is often used in modern opensource software, and is particularly prevalent in test suites, where binary headers and unicode data content are initialized in arrays to test functions.

String Concatenation

GCC will accept the following code, by concatenating the strings:

&lt;code&gt;puts( "abc" "def" );&lt;/code&gt;

This is going to not work on MIPSPro's c89, but will on c99. A tutorial on how to fix it is below:

&lt;code&gt;puts( "abcdef" );&lt;/code&gt;

This can work here, alternatively this would too:
&lt;pre&gt;
char buff[ 255 ];

bzero( buff, 0, 255);

strcat( buff, "abc" );

strcat( buff, "def" );
&lt;/pre&gt;

=====Arithmetic On Pointers=====

The gcc compiler allows pointer arithmetic on void pointers. For example, gcc allows

void *foo;

foo += 5;

When using MIPSpro, the pointer must be cast to a type with a size:

void *foo;

foo = (char*)foo + 5;

lvalues

gcc allows the use of casts as lvalues. For example:

void *foo;

(char*)foo += 5;

When using MIPSpro, casts cannot be lvalues:

void *foo;

foo = (char*)foo + 5;

=====Block Expressions=====

gcc allows block expressions, such as ({x++});. When using MIPSPro compilers, remove the extra parentheses.

=====Portable Types=====

Occasionally code that works on other platforms will compile fine on IRIX, but will misbehave when run. These problems can be difficult to track down, but one thing to check for is assumptions about whether char is signed or unsigned. IRIX compilers default to unsigned. It's recommended to check for this.

Setting up parallel debugging sessions and stepping through the working and non-working code simultaneously to find where they diverge is often helpful.

Alternatively, try to recompile the code with the MIPSPro option -signed in CFLAGS. This will treat variables with type char as if they are signed char.

setenv() missing in IRIX

Raion's libxg library has solved this, see it for an example.

=====POSIX Threads and Reentrancy=====

The pthread implementation under Irix is mostly the standard pthreads - there is however a caveat in the form of #defines that are necessary.

&lt;code&gt;CPPFLAGS="-D_SGI_MP_SOURCE -D_SGI_REENTRANT_FUNCTIONS"&lt;/code&gt;

SGI recommended these back when their technical documentation library was a thing - and certainly the first define alters the behavior of the general error indicator errno. Without _SGI_MP_SOURCE individual threads receive separate and unique errno addresses.

If there is unusual behavior regarding threads not sharing or unexpectedly sharing data, one may be missing one of the above.

=====Line terminators=====

The ANSI specification leaves the determination of valid line terminators to the compiler implementors. MIPSpro allows ^J, while GCC allows both ^J and ^M. The &lt;code&gt;to_unix&lt;/code&gt; command will convert files containing DOS-style ^M line terminators to the UNIX standard ^J form.

=====Pseudo Function Macros=====

gcc allows the non-standard &lt;code&gt;__FUNCTION__&lt;/code&gt; and &lt;code&gt;__PRETTY_FUNCTION__&lt;/code&gt; pseudo-macros. These are not true macros, so one must use &lt;code&gt;_GNUC__&lt;/code&gt; to test for them. As of IRIX 6.5.18, the c99 func macro is available, which expands to a function name.

=====Extern Inline Functions=====

The gcc compiler treats extern inline functions as being extern,while the MIPSpro compilers treat them as inline. To get equivalent behavior, remove the inline keyword.

=====Inline defines in C code=====

Pre-c99 C code often define an INLINE macro being set to &lt;code&gt;inline&lt;/code&gt; MIPSPro cc compiler instead uses &lt;code&gt;__inline&lt;/code&gt; MIPSPro's c99 compiler follows the c99 standard and will inline function with the &lt;code&gt;inline&lt;/code&gt; keyword.

getopt_long() missing in IRIX

Raion had added a compat/getopt.h to libxg

=====Compiler Identification=====

To pass specific code using an identification macro, the &lt;code&gt;__sgi&lt;/code&gt; macro can be used to reliably define MIPSPro-related code (or IRIX specific code in general, this can be combined with gnu macros to make paths for both gcc and MIPSPro)

=====Warning Sanitizing=====

MIPSPro is very pedantic with warnings. This can be used in Makefiles to make it less pedantic and behave more like GCC:
&lt;pre&gt;
NOWARN = -woff 1009,1014,1110,1116,1185,1188,1204,1230,1233 \

-Wl,-woff,85,-woff,84
$(CC) $(NOWARN) ...&lt;/pre&gt;

It is highly encouraged to do a normal pass and capture the warnings it gathers anyways, as these can provide some insight into potential mismatches and other issues.

=== C99 Specifics ===
MIPSPro provides C99 compatibility via the c99 driver.

The C99 implementation in MIPSPro is quite good, but unlike standard cc, which is not C99 compliant, it offers far more features:

=== C++-Style Comments ===
By default, the cc driver does not allow // comments to be used. To use //, either use the c99 driver, or set flag -Xcpluscomm in the CFLAGS.

=== Function Macros ===
As previously stated, all versions of IRIX since 6.5.18 support the function pseudomacro.

=== Variadic Macros ===
Supported in c99

=== Format problems in printf for variables with size_t and ssize_t ===
In MIPSPro one cannot use the format strings %zu for size_t types and %zd for ssize_t types. Use %lu and cast both types to unsigned long to print out these variables. Failure to do so will result in unexpected crashes when the program reaches those printf statements.

More to be added as they are discovered.

== Compiler Drivers ==
The driver commands cc, c99, CC, f90, and f77 call subsystems that compile, optimize, assemble, and link source. This section describes the default behavior for compiler drivers.

At compilation time, it is possible to select one or more options that affect a variety of program development functions, including debugging, profiling, and optimizing. It's also possible to specify the names assigned to output files. Note that some options have default values that apply if not specified.

When one invokes a compiler driver with source files as arguments, the driver calls other commands that compile the source code into object code. It then optimizes the object code (if requested to do so) and links together the object files, the default libraries, and any other libraries specified.

Given a source file foo.c, the default name for the object file is foo.o. The default name for an executable file is a.out. The following example compiles source files foo.c and bar.c with the default options:

&lt;code&gt;% cc foo.c bar.c&lt;/code&gt;

This example produces two object files, foo.o and bar.o, and links them with the default C library, libc , to produce an executable called a.out.</text>
    <sha1>bec1b19af0fcb1d878effff308e3bc7b63f35241</sha1>
  </revision>
  <revision>
    <id>202</id>
    <parentid>189</parentid>
    <timestamp>2025-02-16T21:45:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13187" xml:space="preserve">MIPSPro is the IRIX-native C/C++/FORTRAN compiler that was distributed by SGI for use in IRIX development.

This page serves to document MIPSPro's behavior, characteristics, compatibility, and differences from other UNIX-style cc compilers and the GNU Compiler Collection.

For legacy MIPSPro releases and documentation, see [[IRIS Development Option]] for more info.

=== General ===
MIPSPro is not installed in a standard IRIX install and requires a collection of other discs that contain the compiler, development libraries/header files, toolchain and supporting utilities.

MIPSPro supports three ABIs, O32, N32 and N64 (Not to be confused with the Nintendo 64). The O32 ABI is the MIPSII 32-bit ABI, and stands for Old 32. The N32 ABI is analogous to the Intel x32 ABI used on x64 systems to provide enhancements to 32-bit programs through using 32-bit pointers while offering many of the N64 ABI enhancements over O32. The N64 ABI is the native 64-bit ABI for IRIX.

Several compiler front ends were available, including the C, C++ and FORTRAN compilers. Others may have possibly been available at various points historically.

=== Optimization ===
MIPSPro supports -O0,1,2,3, and fast flags, as well as a number of other optimization/architecture flags:

-mips4 will enable the MIPS IV instruction set

-TARG will enable platform or CPU-specific optimizations

-OPT can tune various optimizations

For a full list, please check: &lt;nowiki&gt;https://irix7.com/techpubs/007-2360-006.pdf&lt;/nowiki&gt;

==== TARG flag ====
The TARG flag controls both platform and CPU specific optimizations and will take a variety of commands:

-TARG:proc=R10000 will, combined with the MIPSIV flag, compile for MIPS IV platforms and enable specific optimizations for the R10000 processors. The resulting binary will run on R5000 and R8000 systems, but will skip the optimizations for those platforms.

-TARG:platform=IP30 will, combined with other flags, enable Octane specific optimizations.

The two commands can be combined as so: -TARG:platform=IP30:proc=R10000 as well as other commands.

==== OPT flag ====
This has a number of useful flags for more carefully optimizing code.

-OPT:space Optimizes the program for size, similar to the GCC -Os flag

-OPT:Olimit=n This sets a cutoff limit on procedure sizes to optimize. Procedures above the set size will be left alone. The compiler will normally during compilation throw notices out advising of potential ways to tune this.

-OPT:alias=value The compilers must normally be very conservative in optimization of memory references involving pointers (especially in C), since aliases (that is, different ways of accessing the same memory) may be very hard to detect. This option may be used to specify that the program being compiled avoids aliasing in various ways. See the above document for various applications.

Other flags are listed in the above document

=== C Programming with MIPSPro ===
Much like GCC and other modern compilers, MIPSPro can be called from the commandline like so:

&lt;code&gt;% cc foo.c&lt;/code&gt;

Where foo.c is a presumably simple test file.

MIPSPro's ABI, compiling and configuration is via &lt;code&gt;/etc/compiler.defaults&lt;/code&gt;. This can be overridden with compile-time flags, or ENV variables. SGI_ABI, for instance, controls the active ABI:

&lt;code&gt;% setenv SGI_ABI -n32&lt;/code&gt;

This will set it to -n32 mode.

==== Strictness ====
MIPSPro is far more strict than GCC about accepting standard C code and its compiler infrastructure is entirely different. Common bad programming techniques that work in GCC may not work on MIPSPro, this section aims to document common pitfalls:

=====Variable Attributes=====

These are not supported, so they have to be patched with #ifdef or removed:

&lt;code&gt;__attribute__(( XXX ))&lt;/code&gt;

This is the structure of these.

One variable attribute can be rewritten to work with MIPSPro: the attribute 'packed' for a struct can be enforced in MIPSPro by placing the struct between two pragma blocks:

&lt;pre&gt;#if defined (__sgi)

+#pragma pack(1)

+#endif

struct {

...

};

&lt;nowiki&gt;#&lt;/nowiki&gt;if defined (__sgi)

+#pragma pack(0)
+#endif
&lt;/pre&gt;

=====Zero Length Arrays=====

This is a GNU extension prior to c99. Using c99 or -c99 flag for cc should allow it to work.

=====Variable Length Arrays=====

Only supported using the c99 driver or -c99.

=====String Literals=====

IRIXNet staff Dexter1 helpfully pointed this out in a forum post:

Shorthand initialization of char a[] = " "; with MIPSpro will go wrong with leading zero bytes. Rewrite that code.

What follows is his example copied mostly-verbatim:
&lt;pre&gt;
&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;stdio.h&gt;

&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;stdlib.h&gt;

&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;memory.h&gt;

int main(void) {

const char a[] = "\0This is a text";

const char b[] = { 0x0, 'T', 'h', 'i', 's', ' ', 'i', 's', ' ', 'a',

' ', 't', 'e', 'x', 't', 0x0 };

const char *c = "\0This is a text";

char buf1[128];

char buf2[128];

char buf3[128];

size_t lena = sizeof(a) - 1;

size_t lenb = sizeof(b) - 1;

size_t lenc = 15;

memcpy(buf1,a,lena);

memcpy(buf2,b,lenb);

memcpy(buf3,c,lenc);

printf("length a : %d, length b %d, length c %d\n", lena, lenb, lenc);

printf("buf11 : %x, buf21 : %x, buf31 : %x\n", buf11, buf21, buf31);

printf("comparing a with buf1 : %d \n", memcmp(a,buf1,lena));

printf("comparing b with buf2 : %d \n", memcmp(b,buf2,lenb));

printf("comparing c with buf3 : %d \n", memcmp(c,buf3,lenc));

printf("comparing buf1 with buf2 : %d \n", memcmp(buf1,buf2,lena));

printf("comparing buf1 with buf3 : %d \n", memcmp(buf1,buf3,lenc));

printf("comparing buf2 with buf3 : %d \n", memcmp(buf2,buf3,lenb));

return 0;
}
&lt;/pre&gt;
Consider this code. The three text containers a, b and c are initialized differently but all should contain "This is a text" preceded and suffixed by a zero byte.

* Container a's type is an array of char. Its lifetime is limited to the main scope and its initialized content gets put on the stack by the compiler.
* Container b is the longer version of a and is also typed array of char.
* Container c is a pointer to a read-only memory block of chars allocated and initialized by the compiler on the heap.

If compiled with MIPSpro cc or c99 and ran, it becomes apparent that array a is not initialized properly. a1 should contain capital 'T' but instead it's a zero byte: once looking at the stack where a is put with a debugger, there is nothing: The preceding zero byte interferes with compiler code and the stack, although it will allocate the correct amount of bytes on the stack, will only contain zeroes.

This 'shorthand' initialization of an array is often used in modern opensource software, and is particularly prevalent in test suites, where binary headers and unicode data content are initialized in arrays to test functions.

String Concatenation

GCC will accept the following code, by concatenating the strings:

&lt;code&gt;puts( "abc" "def" );&lt;/code&gt;

This is going to not work on MIPSPro's c89, but will on c99. A tutorial on how to fix it is below:

&lt;code&gt;puts( "abcdef" );&lt;/code&gt;

This can work here, alternatively this would too:
&lt;pre&gt;
char buff[ 255 ];

bzero( buff, 0, 255);

strcat( buff, "abc" );

strcat( buff, "def" );
&lt;/pre&gt;

=====Arithmetic On Pointers=====

The gcc compiler allows pointer arithmetic on void pointers. For example, gcc allows

void *foo;

foo += 5;

When using MIPSpro, the pointer must be cast to a type with a size:

void *foo;

foo = (char*)foo + 5;

lvalues

gcc allows the use of casts as lvalues. For example:

void *foo;

(char*)foo += 5;

When using MIPSpro, casts cannot be lvalues:

void *foo;

foo = (char*)foo + 5;

=====Block Expressions=====

gcc allows block expressions, such as ({x++});. When using MIPSPro compilers, remove the extra parentheses.

=====Portable Types=====

Occasionally code that works on other platforms will compile fine on IRIX, but will misbehave when run. These problems can be difficult to track down, but one thing to check for is assumptions about whether char is signed or unsigned. IRIX compilers default to unsigned. It's recommended to check for this.

Setting up parallel debugging sessions and stepping through the working and non-working code simultaneously to find where they diverge is often helpful.

Alternatively, try to recompile the code with the MIPSPro option -signed in CFLAGS. This will treat variables with type char as if they are signed char.

setenv() missing in IRIX

Raion's libxg library has solved this, see it for an example.

=====POSIX Threads and Reentrancy=====

The pthread implementation under Irix is mostly the standard pthreads - there is however a caveat in the form of #defines that are necessary.

&lt;code&gt;CPPFLAGS="-D_SGI_MP_SOURCE -D_SGI_REENTRANT_FUNCTIONS"&lt;/code&gt;

SGI recommended these back when their technical documentation library was a thing - and certainly the first define alters the behavior of the general error indicator errno. Without _SGI_MP_SOURCE individual threads receive separate and unique errno addresses.

If there is unusual behavior regarding threads not sharing or unexpectedly sharing data, one may be missing one of the above.

=====Line terminators=====

The ANSI specification leaves the determination of valid line terminators to the compiler implementors. MIPSpro allows ^J, while GCC allows both ^J and ^M. The &lt;code&gt;to_unix&lt;/code&gt; command will convert files containing DOS-style ^M line terminators to the UNIX standard ^J form.

=====Pseudo Function Macros=====

gcc allows the non-standard &lt;code&gt;__FUNCTION__&lt;/code&gt; and &lt;code&gt;__PRETTY_FUNCTION__&lt;/code&gt; pseudo-macros. These are not true macros, so one must use &lt;code&gt;_GNUC__&lt;/code&gt; to test for them. As of IRIX 6.5.18, the c99 func macro is available, which expands to a function name.

=====Extern Inline Functions=====

The gcc compiler treats extern inline functions as being extern,while the MIPSpro compilers treat them as inline. To get equivalent behavior, remove the inline keyword.

=====Inline defines in C code=====

Pre-c99 C code often define an INLINE macro being set to &lt;code&gt;inline&lt;/code&gt; MIPSPro cc compiler instead uses &lt;code&gt;__inline&lt;/code&gt; MIPSPro's c99 compiler follows the c99 standard and will inline function with the &lt;code&gt;inline&lt;/code&gt; keyword.

getopt_long() missing in IRIX

Raion had added a compat/getopt.h to libxg

=====Compiler Identification=====

To pass specific code using an identification macro, the &lt;code&gt;__sgi&lt;/code&gt; macro can be used to reliably define MIPSPro-related code (or IRIX specific code in general, this can be combined with gnu macros to make paths for both gcc and MIPSPro)

=====Warning Sanitizing=====

MIPSPro is very pedantic with warnings. This can be used in Makefiles to make it less pedantic and behave more like GCC:
&lt;pre&gt;
NOWARN = -woff 1009,1014,1110,1116,1185,1188,1204,1230,1233 \

-Wl,-woff,85,-woff,84
$(CC) $(NOWARN) ...&lt;/pre&gt;

It is highly encouraged to do a normal pass and capture the warnings it gathers anyways, as these can provide some insight into potential mismatches and other issues.

=== C99 Specifics ===
MIPSPro provides C99 compatibility via the c99 driver.

The C99 implementation in MIPSPro is quite good, but unlike standard cc, which is not C99 compliant, it offers far more features:

=== C++-Style Comments ===
By default, the cc driver does not allow // comments to be used. To use //, either use the c99 driver, or set flag -Xcpluscomm in the CFLAGS.

=== Function Macros ===
As previously stated, all versions of IRIX since 6.5.18 support the function pseudomacro.

=== Variadic Macros ===
Supported in c99

=== Format problems in printf for variables with size_t and ssize_t ===
In MIPSPro one cannot use the format strings %zu for size_t types and %zd for ssize_t types. Use %lu and cast both types to unsigned long to print out these variables. Failure to do so will result in unexpected crashes when the program reaches those printf statements.

More to be added as they are discovered.

== Compiler Drivers ==
The driver commands cc, c99, CC, f90, and f77 call subsystems that compile, optimize, assemble, and link source. This section describes the default behavior for compiler drivers.

At compilation time, it is possible to select one or more options that affect a variety of program development functions, including debugging, profiling, and optimizing. It's also possible to specify the names assigned to output files. Note that some options have default values that apply if not specified.

When one invokes a compiler driver with source files as arguments, the driver calls other commands that compile the source code into object code. It then optimizes the object code (if requested to do so) and links together the object files, the default libraries, and any other libraries specified.

Given a source file foo.c, the default name for the object file is foo.o. The default name for an executable file is a.out. The following example compiles source files foo.c and bar.c with the default options:

&lt;code&gt;% cc foo.c bar.c&lt;/code&gt;

This example produces two object files, foo.o and bar.o, and links them with the default C library, libc , to produce an executable called a.out.

[[Category:Compilers]]</text>
    <sha1>d87ecb1694728384879af165b5d321cb42c9186d</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>IRIS Development Option</title>
  <ns>0</ns>
  <id>103</id>
  <revision>
    <id>190</id>
    <parentid>125</parentid>
    <timestamp>2025-02-16T21:37:37Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="994" xml:space="preserve">IDO, also known by its backend name of uopt, is an IRIX-based compiler used on IRIX versions prior to 6.5 and compiler versions prior to 7.2. However it is unknown when the compiler backend switched from uopt to [[MIPSPro]] truly. Estimation is around version 7.3. 

IDO was famously a default compiler for many Nintendo 64 consoles and includes support for the MIPS R4300i CPU and its eccentricities. MIPSPro 7.3 and 7.4 exclude these options. 

==== Known IDO versions ====
IDO has the following known versions:

* IRIS Development Option 4.0
* IRIS Development Option 4.1.x
* Trusted IRIS Development Option 4.0.5
* IRIS Development Option 5.0
* IRIS Development Option 5.1
* IRIS Development Option 5.3
* IRIS Development Option 6.0
* IRIS Development Option 6.1
* IRIS Development Option 7.1
* IRIS Development Option 7.1.1

==== ABI Support ====
Later versions intended for IRIX 6.x include support for n64 ABI and potentially some support for n32 ABIs. All prior versions are purely o32.</text>
    <sha1>0ee84cd0e98198b9882dcce79f26cd070bc5e811</sha1>
  </revision>
  <revision>
    <id>201</id>
    <parentid>190</parentid>
    <timestamp>2025-02-16T21:44:29Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1060" xml:space="preserve">IDO, also known by its backend name of uopt, is an IRIX-based compiler used on IRIX versions prior to 6.5 and compiler versions prior to 7.2. However it is unknown when the compiler backend switched from uopt to [[MIPSPro]] truly. Estimation is around version 7.3. 

IDO was famously a default compiler for many Nintendo 64 consoles and includes support for the MIPS R4300i CPU and its eccentricities. MIPSPro 7.3 and 7.4 exclude these options. 

==== Known IDO versions ====
IDO has the following known versions:

* IRIS Development Option 4.0
* IRIS Development Option 4.1.x
* Trusted IRIS Development Option 4.0.5
* IRIS Development Option 5.0
* IRIS Development Option 5.1
* IRIS Development Option 5.3
* IRIS Development Option 6.0
* IRIS Development Option 6.1
* IRIS Development Option 7.1
* IRIS Development Option 7.1.1

==== ABI Support ====
Later versions intended for IRIX 6.x include support for n64 ABI and potentially some support for n32 ABIs. All prior versions are purely o32.

[[Category:Compilers]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>d0e9dae79e2c8fd9b0b2e734998e5c7d98929747</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>191</id>
    <parentid>132</parentid>
    <timestamp>2025-02-16T21:39:29Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3594" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>3dd5f9caa26545cf95c56061575b97247d4835f0</sha1>
  </revision>
  <revision>
    <id>194</id>
    <parentid>191</parentid>
    <timestamp>2025-02-16T21:41:31Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3642" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-3.x|4D1-2.x]]

• [[4D1-3.x|4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>9c62f6b92d97dc084ae58009266eda2cca89c027</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Category:Stubs</title>
  <ns>14</ns>
  <id>110</id>
  <revision>
    <id>192</id>
    <timestamp>2025-02-16T21:40:12Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Stubs are articles that lack sufficient detail or quality"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="57" xml:space="preserve">Stubs are articles that lack sufficient detail or quality</text>
    <sha1>5c50f2aff6586bd85d30451a10658de95a9cb422</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Category:No-Images</title>
  <ns>14</ns>
  <id>111</id>
  <revision>
    <id>193</id>
    <timestamp>2025-02-16T21:41:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Pages needing images"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">Pages needing images</text>
    <sha1>8f8120e27c416c0ef9f759878719a80f15ab4632</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>IRIX 6.5</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>195</id>
    <parentid>89</parentid>
    <timestamp>2025-02-16T21:41:58Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1607" xml:space="preserve">IRIX 6.5 is the final major version of IRIX released first in 1998. Further incremental improvements were made from 1998 to 2006, with security updates ending in 2013 under Rackable Systems. 

==== Improvements over IRIX 6.2 ====
IRIX 6.5's most notable improvement is standardized distribution. No more is a specific IRIX version needed for a specific machine. It includes support for all 64-bit capable SGIs with a few exceptions (e.g. the Crimson). 

====== New Features: ======

* OpenGL 1.1 support for all systems supported. 
* Desktop now called IRIX Interactive Desktop
* Improved security for remote X and other subsystems (safer defaults)
* Gigabit support
* Improved C library support. Compiler now supports C99. 
* MIPSPro replaces IDO/uopt as the main compiler backend.
* Later versions have Firewire and USB support.
* Later versions added OpenGL 1.2 support

==== Lifecycle ====
From 1998 to 2006 a new point release was released every quarter from .1 to .30. Security updates continued for 6.5.22 and higher until 2013. Shortly thereafter, SGI's Supportfolio site went offline. 

==== System Support ====
IRIX 6.5 through .22 supported all of the following systems:

* [[IRIS Indigo]] R4000
* [[Onyx|Onyx/Challenge R4000-R10000]]
* [[Indy]]
* [[Indigo2]]
* [[Onyx2]]
* [[Octane]]
* [[Origin 2000|Origin 2000 and 200]]
* [[Challenge S]]
* [[O2]]
* [[Fuel]]
* [[Origin 300]]
* [[Origin 350]]
* [[Origin 3000]]
* [[Tezro]]
* [[Onyx4]]

After 6.5.22, support for the following systems was dropped:

* IRIS Indigo
* Indy
* Indigo2
* Onyx/Challenge

[[Category:OS-Versions]]
[[Category:No-Images]]</text>
    <sha1>7c67878b09dc7d700ec6f8c862c83e78d43e4a34</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>Category:OS-Versions</title>
  <ns>14</ns>
  <id>112</id>
  <revision>
    <id>196</id>
    <timestamp>2025-02-16T21:42:24Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "OS Versions documented by TechPubs"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="34" xml:space="preserve">OS Versions documented by TechPubs</text>
    <sha1>beb2c4f0fb1b92c8d1eed0672c03b7b0e98fd079</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>IRIX 6.2</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>197</id>
    <parentid>90</parentid>
    <timestamp>2025-02-16T21:43:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="725" xml:space="preserve">IRIX 6.2 was released in early 1996 for multiple SGI desktops. The 6.x series is based on late 5.x code with 64-bit support in the OS being its major killer app. IRIX 6.3 and 6.4 are special releases of 6.2 for the O2 and Octane, Origin2000/Onyx2 and Origin 200. 

==== Changes ====

* 64-bit kernel support and the new n32 ABI. 
* Removal of all 32-bit only IRIX platforms from the supported list (i.e. R2000 and R3000 systems). 
* Improved system stability. 
* XFS file system is default. EFS no longer supported for system installs. 
* VNode/VFS system imported, enabling new filesystems to be more easily added. 
* COFF applications no longer supported.

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>5479b72ae6a99593b273e8c8b4d103915d66d835</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>IRIX 5.3</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>198</id>
    <parentid>91</parentid>
    <timestamp>2025-02-16T21:43:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="316" xml:space="preserve">IRIX 5.3 was released in November of 1994, the last of the IRIX 5.x series that began in March of 1993. IRIX 5.3 improved system stability and introduced many features of IRIX such as XFS (with the XFS release in 12/1994), ELF executables and more.

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>c7aea47fbfa0752da9c2e1ebf94761cb7128594d</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>IRIX 4.0</title>
  <ns>0</ns>
  <id>83</id>
  <revision>
    <id>199</id>
    <parentid>92</parentid>
    <timestamp>2025-02-16T21:43:57Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="390" xml:space="preserve">IRIX 4.0, introduced in September of 1991 with the IRIS Indigo workstation was the first version of IRIX to be officially named "IRIX." Replacing the [[4Sight]] NeWS-based system, X11R4 using the IRIS Desktop (later called IRIX Interactive Desktop), and was the first version to be released on CD, as opposed to QIC tape.


[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>adeda108f12d37d060764c3016d3a0ce6261353e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:13:56+00|153">
  <title>RISC/OS</title>
  <ns>0</ns>
  <id>97</id>
  <revision>
    <id>200</id>
    <parentid>116</parentid>
    <timestamp>2025-02-16T21:44:09Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="305" xml:space="preserve">RISC/OS was an early UNIX produced by MIPS Computer Systems, and a predecessor of both 4D1 and IRIX. Unlike [[GL2]], RISC/OS was a dual-universe system with both 4.3BSD and System V Release 3 support. It did not support shared libraries.

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>fe998b3d5009c19ebdd6962aea3e575677baab3c</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>GCC</title>
  <ns>0</ns>
  <id>102</id>
  <revision>
    <id>203</id>
    <parentid>124</parentid>
    <timestamp>2025-02-16T21:45:20Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5229" xml:space="preserve">The GNU Compiler Collection is officially supported on IRIX through GCC 4.7. Unofficial support by various groups has resulted in versions as high as 9.5 being successfully built. 

=== Officially Supported Versions ===
GCC 3.4.6 is in the Nekoware collection, and is one of the older versions to survive linkrot. GCC 3.3 was distributed via SGI freeware. 4.x versions include 4.6.3 in [https://www.osarchive.org/os/irix/gnu Nekomimiware] (A play on Nekoware's name), and GCC 4.7.1 is packaged by Nekoware as well.  An older version supported GNAT and GNU Java (4.4.x)

=== Unofficial Versions ===
GCC 4.7.4 is cross-compilable as is 8.2 and 9.2 (via SGUG RSE). Raion has made GCC 6.5.0 with C, C++ and Fortran available with fixes applied to improve the compiler. He also released an experimental GCC 9.5.0 in February of 2025. 

=== GCC 6.5.0 Build ===
A minimum compiler version of approximately GCC 4.4.x is required to build GCC 6.5.0 successfully on IRIX, this has not been thoroughly tested. Raion reports using GCC 4.7.4 with fixincludes applied to build IRIX. 

==== Requirements: ====
GCC 4.4.x or later

GMP 6.x

MPC 1.x

MPFR 3.1.x

ISL 0.18 (for Graphite Loop Optimization. 

Binutils 2.23.2 (Link to the  [http://contrib.irixnet.org/raion/gcc-prepatched/binutils-2.23.2.tar.gz prepatched code])

zlib 1.x

libffi version 3.3.1

Bash, any version for compiling GCC 

star or libarchive tar or gnu tar to extract. 

Build zlib and libffi into the prefix for GCC. Make sure they're in the search paths to get picked up. 

Per [http://contrib.irixnet.org/raion/relnotes/neko_gcc6.txt the relnotes], build binutils with the specific commands.

Per the relnotes, prepare the build environment for GCC. Make sure the system ncargs are set appropriately as well. get into bash, set the env up, and run the build and checks. &lt;pre&gt;
### TEST RESULTS
                === gcc Summary ===

# of expected passes            81595
# of unexpected failures        470
# of unexpected successes       15
# of expected failures          171
# of unresolved testcases       17
# of unsupported tests          1806

Failures: https://pastebin.com/eKwMrgUT

                === g++ Summary ===                                                                                                                                                                                                              
                                                                                                                                                                                                                                                 
# of expected passes            93269                                                                                                                                                                                                            
# of unexpected failures        14                                                                                                                                                                                                               
# of expected failures          313                                                                                                                                                                                                              
# of unsupported tests          4151                                                                                                                                                                                                             

Failures: https://pastebin.com/mHunc8bD

                === libstdc++ Summary ===

# of expected passes            9471
# of unexpected failures        119
# of expected failures          66
# of unresolved testcases       2
# of unsupported tests          967

Failures: https://pastebin.com/a0vnnMQi

                === gfortran Summary ===

# of expected passes            42294
# of unexpected failures        124
# of expected failures          78
# of unsupported tests          97

Failures: https://pastebin.com/C30hwj0a

&lt;/pre&gt;

=== GCC 9.5.0 Build ===
A minimum compiler version of approximately GCC 4.6.x is required to build GCC 9.5.0 successfully on IRIX, this has not been thoroughly tested. Raion reports using GCC 6.5.0 with fixincludes applied to build IRIX. 

==== Requirements: ====
GCC 4.4.x or later

GMP 6.x

MPC 1.0.x

MPFR 3.1.x

ISL 0.18 (for Graphite Loop Optimization. 

Binutils 2.23.2 (Link to the [http://contrib.irixnet.org/raion/gcc-prepatched/binutils-2.23.2.tar.gz prepatched code])

zlib 1.x

libffi version 3.3.1

Bash, any version for compiling GCC

star or libarchive tar or gnu tar to extract. 

[https://pastebin.com/T4nc2rhd Raion's 9.5.0 Patch]

Build zlib and libffi into the prefix for GCC. Make sure they're in the search paths to get picked up. 

Per the 6.5.0 relnotes, build binutils with the specific commands.

Make sure the system ncargs are set appropriately as well. get into bash, set the env up, and run the build. Testsuites skipped for time reasons. 

Seemed to work fine on first glance.

[[Category:Hardware]]
[[Category:No-Images]]
[[Category:Open-Source-Software]]</text>
    <sha1>99aa9f305df88e96a38da64f3f4fe96ce210c662</sha1>
  </revision>
  <revision>
    <id>245</id>
    <parentid>203</parentid>
    <timestamp>2025-02-17T02:35:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5250" xml:space="preserve">The GNU Compiler Collection is officially supported on IRIX through GCC 4.7. Unofficial support by [[SGUG|various]] [[IRIXNet|groups]] has resulted in versions as high as 9.5 being successfully built. 

=== Officially Supported Versions ===
GCC 3.4.6 is in the Nekoware collection, and is one of the older versions to survive linkrot. GCC 3.3 was distributed via SGI freeware. 4.x versions include 4.6.3 in [https://www.osarchive.org/os/irix/gnu Nekomimiware] (A play on Nekoware's name), and GCC 4.7.1 is packaged by Nekoware as well.  An older version supported GNAT and GNU Java (4.4.x)

=== Unofficial Versions ===
GCC 4.7.4 is cross-compilable as is 8.2 and 9.2 (via SGUG RSE). Raion has made GCC 6.5.0 with C, C++ and Fortran available with fixes applied to improve the compiler. He also released an experimental GCC 9.5.0 in February of 2025. 

=== GCC 6.5.0 Build ===
A minimum compiler version of approximately GCC 4.4.x is required to build GCC 6.5.0 successfully on IRIX, this has not been thoroughly tested. Raion reports using GCC 4.7.4 with fixincludes applied to build IRIX. 

==== Requirements: ====
GCC 4.4.x or later

GMP 6.x

MPC 1.x

MPFR 3.1.x

ISL 0.18 (for Graphite Loop Optimization. 

Binutils 2.23.2 (Link to the  [http://contrib.irixnet.org/raion/gcc-prepatched/binutils-2.23.2.tar.gz prepatched code])

zlib 1.x

libffi version 3.3.1

Bash, any version for compiling GCC 

star or libarchive tar or gnu tar to extract. 

Build zlib and libffi into the prefix for GCC. Make sure they're in the search paths to get picked up. 

Per [http://contrib.irixnet.org/raion/relnotes/neko_gcc6.txt the relnotes], build binutils with the specific commands.

Per the relnotes, prepare the build environment for GCC. Make sure the system ncargs are set appropriately as well. get into bash, set the env up, and run the build and checks. &lt;pre&gt;
### TEST RESULTS
                === gcc Summary ===

# of expected passes            81595
# of unexpected failures        470
# of unexpected successes       15
# of expected failures          171
# of unresolved testcases       17
# of unsupported tests          1806

Failures: https://pastebin.com/eKwMrgUT

                === g++ Summary ===                                                                                                                                                                                                              
                                                                                                                                                                                                                                                 
# of expected passes            93269                                                                                                                                                                                                            
# of unexpected failures        14                                                                                                                                                                                                               
# of expected failures          313                                                                                                                                                                                                              
# of unsupported tests          4151                                                                                                                                                                                                             

Failures: https://pastebin.com/mHunc8bD

                === libstdc++ Summary ===

# of expected passes            9471
# of unexpected failures        119
# of expected failures          66
# of unresolved testcases       2
# of unsupported tests          967

Failures: https://pastebin.com/a0vnnMQi

                === gfortran Summary ===

# of expected passes            42294
# of unexpected failures        124
# of expected failures          78
# of unsupported tests          97

Failures: https://pastebin.com/C30hwj0a

&lt;/pre&gt;

=== GCC 9.5.0 Build ===
A minimum compiler version of approximately GCC 4.6.x is required to build GCC 9.5.0 successfully on IRIX, this has not been thoroughly tested. Raion reports using GCC 6.5.0 with fixincludes applied to build IRIX. 

==== Requirements: ====
GCC 4.4.x or later

GMP 6.x

MPC 1.0.x

MPFR 3.1.x

ISL 0.18 (for Graphite Loop Optimization. 

Binutils 2.23.2 (Link to the [http://contrib.irixnet.org/raion/gcc-prepatched/binutils-2.23.2.tar.gz prepatched code])

zlib 1.x

libffi version 3.3.1

Bash, any version for compiling GCC

star or libarchive tar or gnu tar to extract. 

[https://pastebin.com/T4nc2rhd Raion's 9.5.0 Patch]

Build zlib and libffi into the prefix for GCC. Make sure they're in the search paths to get picked up. 

Per the 6.5.0 relnotes, build binutils with the specific commands.

Make sure the system ncargs are set appropriately as well. get into bash, set the env up, and run the build. Testsuites skipped for time reasons. 

Seemed to work fine on first glance.

[[Category:Hardware]]
[[Category:No-Images]]
[[Category:Open-Source-Software]]</text>
    <sha1>c3a40d2c9d055718bd69001592f3a80307ba8037</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>SGI Freeware</title>
  <ns>0</ns>
  <id>96</id>
  <revision>
    <id>204</id>
    <parentid>112</parentid>
    <timestamp>2025-02-16T21:45:37Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="228" xml:space="preserve">SGI Freeware was an IRIX-compatible distribution of free and open source software built and distributed by SGI employees, and distributed on SGI media.

[[Category:Open-Source-Software]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>3d5cf46e80d53c0cb6666d7df37dedc0c445d4d3</sha1>
  </revision>
  <revision>
    <id>244</id>
    <parentid>204</parentid>
    <timestamp>2025-02-17T02:34:48Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="339" xml:space="preserve">SGI Freeware was an IRIX-compatible distribution of free and open source software built and distributed by SGI employees, and distributed on SGI media.

Distributed on 4 CDs, it hosted a variety of software and directly served as the inspiration for [[Nekoware]]

[[Category:Open-Source-Software]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>8607d4fbb3792dacf34baf9f115a7603f02583d4</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>Nekoware</title>
  <ns>0</ns>
  <id>99</id>
  <revision>
    <id>205</id>
    <parentid>119</parentid>
    <timestamp>2025-02-16T21:45:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="199" xml:space="preserve">Nekoware is a community project started on Nekochan.net that created and offered MIPS4 packages for IRIX 6.5.21 or higher.

[[Category:Open-Source-Software]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>4e599a28b6924e07eb74bb6b66cbdfac2ee1e303</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>SGUG RSE</title>
  <ns>0</ns>
  <id>101</id>
  <revision>
    <id>206</id>
    <parentid>122</parentid>
    <timestamp>2025-02-16T21:46:16Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="757" xml:space="preserve">SGUG RSE is a community effort of the Silicon Graphics User Group to develop software for IRIX using a ported version of RPM, along with tdnf and microdnf to provide package management and resolution. It essentially installs itself as a package without any interaction with the larger system. 

==== Toolchain ====
RSE uses GCC 9 which can cross compile with distcc on x86 systems. It uses RPM SPEC files (not to be confused with SGI SPEC files) to generate SRPMs. It is based on Fedora 31. 

==== Packages ====
As of 2025, RSE is still experimental but boasts over 1,000 "packages" of software, of which many are games, media and other software that is of relevance to SGI users.

[[Category:Open-Source-Software]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>481639dd0518fa64efc0fbb34142f8d6aaf674df</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>RISC/OS</title>
  <ns>0</ns>
  <id>97</id>
  <revision>
    <id>207</id>
    <parentid>200</parentid>
    <timestamp>2025-02-16T21:47:35Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="362" xml:space="preserve">RISC/OS was an early UNIX produced by MIPS Computer Systems, and a predecessor of both 4D1 and IRIX. Unlike [[GL2]], RISC/OS was a dual-universe system with both 4.3BSD and System V Release 3 support. It did not support shared libraries. When SGI purchased MIPS, it was succeeded by [[4D1-1.x]]

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>d601e29d206f6f4ffcd1cfb9886b5f9aba8ea600</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>IRIX 4.0</title>
  <ns>0</ns>
  <id>83</id>
  <revision>
    <id>208</id>
    <parentid>199</parentid>
    <timestamp>2025-02-16T21:48:04Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="402" xml:space="preserve">IRIX 4.0, introduced in September of 1991 with the IRIS Indigo workstation was the first version of IRIX to be officially named "IRIX." Replacing the [[4Sight]] NeWS-based [[4D1-3.x]] system, X11R4 using the IRIS Desktop (later called IRIX Interactive Desktop), and was the first version to be released on CD, as opposed to QIC tape.


[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>bd30d45e7266c48f7385fcb06aef4bb14b951a3d</sha1>
  </revision>
  <revision>
    <id>232</id>
    <parentid>208</parentid>
    <timestamp>2025-02-17T02:04:49Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="502" xml:space="preserve">IRIX 4.0, introduced in September of 1991 with the IRIS Indigo workstation was the first version of IRIX to be officially named "IRIX." Replacing the [[4Sight]] NeWS-based [[4D1-3.x]] system, X11R4 using the IRIS Desktop (later called IRIX Interactive Desktop), and was the first version to be released on CD, as opposed to QIC tape.

[[File:Irix-4.0.1-img1.gif|thumb|IRIX 4.0.1 Desktop with IRIS Showcase. Courtesy of sgistuff.net]]


[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>9284b0d3fdcfcc966f9eaf90c169697fbdacdd5c</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>IRIX 6.5</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>209</id>
    <parentid>195</parentid>
    <timestamp>2025-02-16T21:48:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1631" xml:space="preserve">IRIX 6.5 is the final major version of IRIX released first in 1998 to replace [[IRIX 6.2]]. Further incremental improvements were made from 1998 to 2006, with security updates ending in 2013 under Rackable Systems. 

==== Improvements over IRIX 6.2 ====
IRIX 6.5's most notable improvement is standardized distribution. No more is a specific IRIX version needed for a specific machine. It includes support for all 64-bit capable SGIs with a few exceptions (e.g. the Crimson). 

====== New Features: ======

* OpenGL 1.1 support for all systems supported. 
* Desktop now called IRIX Interactive Desktop
* Improved security for remote X and other subsystems (safer defaults)
* Gigabit support
* Improved C library support. Compiler now supports C99. 
* MIPSPro replaces IDO/uopt as the main compiler backend.
* Later versions have Firewire and USB support.
* Later versions added OpenGL 1.2 support

==== Lifecycle ====
From 1998 to 2006 a new point release was released every quarter from .1 to .30. Security updates continued for 6.5.22 and higher until 2013. Shortly thereafter, SGI's Supportfolio site went offline. 

==== System Support ====
IRIX 6.5 through .22 supported all of the following systems:

* [[IRIS Indigo]] R4000
* [[Onyx|Onyx/Challenge R4000-R10000]]
* [[Indy]]
* [[Indigo2]]
* [[Onyx2]]
* [[Octane]]
* [[Origin 2000|Origin 2000 and 200]]
* [[Challenge S]]
* [[O2]]
* [[Fuel]]
* [[Origin 300]]
* [[Origin 350]]
* [[Origin 3000]]
* [[Tezro]]
* [[Onyx4]]

After 6.5.22, support for the following systems was dropped:

* IRIS Indigo
* Indy
* Indigo2
* Onyx/Challenge

[[Category:OS-Versions]]
[[Category:No-Images]]</text>
    <sha1>e988d0064235d4d3524df1390f3845151c9c770d</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>IRIX 6.2</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>210</id>
    <parentid>197</parentid>
    <timestamp>2025-02-16T21:49:12Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="761" xml:space="preserve">IRIX 6.2 was released in early 1996 for multiple SGI desktops. The 6.x series is based on late 5.x code with 64-bit support in the OS being its major killer app. IRIX 6.3 and 6.4 are special releases of 6.2 for the O2 and Octane, Origin2000/Onyx2 and Origin 200. 6.2 is based on [[IRIX 5.3]] code.  

==== Changes ====

* 64-bit kernel support and the new n32 ABI. 
* Removal of all 32-bit only IRIX platforms from the supported list (i.e. R2000 and R3000 systems). 
* Improved system stability. 
* XFS file system is default. EFS no longer supported for system installs. 
* VNode/VFS system imported, enabling new filesystems to be more easily added. 
* COFF applications no longer supported.

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>42366fe029c7c0dda0486ab231c6034a4a0f6bfb</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>IRIX 5.3</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>211</id>
    <parentid>198</parentid>
    <timestamp>2025-02-16T21:50:10Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="399" xml:space="preserve">IRIX 5.3 was released in November of 1994, the last of the IRIX 5.x series that began in March of 1993. IRIX 5.3 improved system stability and introduced many features of IRIX such as XFS (with the XFS release in 12/1994), ELF executables and more. It replaced [[IRIX 4.0]], and maintains compatibility with IRIX 4.0 by and large. 

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>f6d51c571afff94cceab9aaef7c3cee2c1e874c1</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>4D1-3.x</title>
  <ns>0</ns>
  <id>113</id>
  <revision>
    <id>212</id>
    <timestamp>2025-02-16T21:50:48Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "4D1-3.x was the final release of the 4D1 systems before they were officially called IRIX. It is also the final version to use [[4Sight]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="136" xml:space="preserve">4D1-3.x was the final release of the 4D1 systems before they were officially called IRIX. It is also the final version to use [[4Sight]]</text>
    <sha1>207fd0e4b04080339171219db2d2d94d3f670fea</sha1>
  </revision>
  <revision>
    <id>229</id>
    <parentid>212</parentid>
    <timestamp>2025-02-16T22:43:15Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="204" xml:space="preserve">4D1-3.x was the final release of the 4D1 systems before they were officially called IRIX. It is also the final version to use [[4Sight]]

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>6334be4feaa759e2f052cc6ece1ca6910c158d1c</sha1>
  </revision>
  <revision>
    <id>235</id>
    <parentid>229</parentid>
    <timestamp>2025-02-17T02:07:54Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="306" xml:space="preserve">4D1-3.x was the final release of the 4D1 systems before they were officially called IRIX. It is also the final version to use [[4Sight]].

[[File:4d1-3.3-Demos.gif|left|thumb|4D1 Demo Set]]
[[File:4d1-3.3-term.gif|thumb|4D1 wsh terminal]]

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>5957aaa3f9002d54060de8c991822be07a9650e8</sha1>
  </revision>
  <revision>
    <id>238</id>
    <parentid>235</parentid>
    <timestamp>2025-02-17T02:12:18Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="283" xml:space="preserve">4D1-3.x was the final release of the 4D1 systems before they were officially called IRIX. It is also the final version to use [[4Sight]].

[[File:4d1-3.3-Demos.gif|left|thumb|4D1 Demo Set]]
[[File:4d1-3.3-term.gif|thumb|4D1 wsh terminal]]

[[Category:OS-Versions]]
[[Category:Stubs]]</text>
    <sha1>82688c4bac14d31c5da3b3b0c650d24997b04311</sha1>
  </revision>
  <revision>
    <id>248</id>
    <parentid>238</parentid>
    <timestamp>2025-02-20T18:01:27Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="333" xml:space="preserve">4D1-3.x was the final release of the 4D1 systems before they were officially called IRIX. It is also the final version to use [[4Sight]].

[[File:4d1-3.3-Demos.gif|left|thumb|4D1 Demo Set courtesy of sgistuff.net]]
[[File:4d1-3.3-term.gif|thumb|4D1 wsh terminal courtesy of sgistuff.net]]

[[Category:OS-Versions]]
[[Category:Stubs]]</text>
    <sha1>3e1d7a9173a66e3fc7dcb47e22e28f3c08b78531</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>213</id>
    <parentid>194</parentid>
    <timestamp>2025-02-16T21:51:21Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* 4D1 Versions */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3626" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-2.x]]

• [[4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>bc9edfc5fa783236b68d2767385fd639f52b7626</sha1>
  </revision>
  <revision>
    <id>214</id>
    <parentid>213</parentid>
    <timestamp>2025-02-16T22:07:07Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>/* MIPS-based SGIs (IRIX era) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3720" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-2.x]]

• [[4D1-1.x]]

===== GL2 Versions =====

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>cf00f9ce37ed948543e007199d07e2dcfe851be3</sha1>
  </revision>
  <revision>
    <id>218</id>
    <parentid>214</parentid>
    <timestamp>2025-02-16T22:24:03Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* GL2 Versions */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3753" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

• [[4D1-2.x]]

• [[4D1-1.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>a92f94c9b5d3c57f0590b7970a86c11e1fae6d7f</sha1>
  </revision>
  <revision>
    <id>222</id>
    <parentid>218</parentid>
    <timestamp>2025-02-16T22:34:23Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* 4D1 Versions */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3719" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>dc610c934d8b67c738fe3f95041a7afc43629669</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>Open Source Software</title>
  <ns>0</ns>
  <id>114</id>
  <revision>
    <id>215</id>
    <timestamp>2025-02-16T22:10:15Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "SGI and the community have offered several flavors of "ware" for IRIX. A list of them and what they focus on is here.   === For IRIX 6.5 === [[IRIX 6.5]] by far has the most editions of software for it.   === For 6.2/5.3 === [http://tgcware.irixnet.org/ TGCWare] has set the bar for this. As it has been frozen since the 2010s, we linked to the IRIXNet mirror. Please only use HTTP, that mirror doesn't support SSL."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="415" xml:space="preserve">SGI and the community have offered several flavors of "ware" for IRIX. A list of them and what they focus on is here. 

=== For IRIX 6.5 ===
[[IRIX 6.5]] by far has the most editions of software for it. 

=== For 6.2/5.3 ===
[http://tgcware.irixnet.org/ TGCWare] has set the bar for this. As it has been frozen since the 2010s, we linked to the IRIXNet mirror. Please only use HTTP, that mirror doesn't support SSL.</text>
    <sha1>37526bdd076bac946769e43682511658667a5300</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>Fuel</title>
  <ns>0</ns>
  <id>115</id>
  <revision>
    <id>216</id>
    <timestamp>2025-02-16T22:12:18Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The Silicon Graphics Fuel, introduced in 2002, was intended to be a single-CPU midrange solution for those customers who did not need multiple-CPU capability, thus offering a much cheaper system compared to a baseline Tezro or top-spec single-CPU [[Octane]]. Contrary to popular belief, Fuel was not a successor to [[O2]]. SGI never made a follow-on to O2; a new system was designed (internally known as the Banana2000 or b2k) but was never developed beyond a prototype.The F..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5918" xml:space="preserve">The Silicon Graphics Fuel, introduced in 2002, was intended to be a single-CPU midrange solution for those customers who did not need multiple-CPU capability, thus offering a much cheaper system compared to a baseline Tezro or top-spec single-CPU [[Octane]]. Contrary to popular belief, Fuel was not a successor to [[O2]]. SGI never made a follow-on to O2; a new system was designed (internally known as the Banana2000 or b2k) but was never developed beyond a prototype.The Fuel has a somewhat contentious reputation in the enthusiast community. In terms of form-factor and internal design, it is the most "PC-like" of the MIPS workstations, sharing much of its design with the Visual Workstation 230. Due to SGI's need to cut costs the Fuel is also likely the most error-prone workstation that SGI produced, with frequent failures of power supplies, mainboards, and environmental monitoring which most heavily plagued early revisions. The frequent failures also means a shortage of available parts, and what parts are available are expensive. So while the Fuel was meant to be a reduced-cost version of the Origin 300 architecture, it is actually the most expensive MIPS desktop to own.

=== Features ===
Fuel shares the IP35-architecture with Origin 300, Origin 350, Origin 3000, Onyx 3000 and Tezro systems.In terms of design, it is closest to a single-node Origin 300 with graphics, based on the environmental monitoring and other support chips.

The design is very similar to a standard ATX PC with the exception of the memory/CPU positions and the XIO2, used for graphics, being below the PCI-X expansion slots, meaning the board is longer and wider than a typical ATX motherboard.

==== CPU ====
The Fuel is a single processor system and can take either:

* One R14000 CPU at either 500 or 600MHz
* One R16000 CPU at 700, 800 or (rarely) 900Mhz

==== Memory ====
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Origin 300, Origin 350, and the Tezro. There are a total of four slots, organized into two banks of two slots. This results in a memory capacity from 512 MBytes to 4 Gbytes total system memory.

All DIMMS for the Fuel use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory, which remains unused in the Fuel. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

==== Graphics ====
The Fuel can have one XIO 2 graphics card, either the V10 configuration with 32MB of texture memory or the V12 with 128MB of texture memory. A dual-channel display card can be attached to offer dual head display.

==== I/O ====
Internally, the boot drive attaches to the mainboard with a 68-pin SCSI cable. Unfortunately, the connector on the mainboard itself is *not* a standard 68-pin connector and is actually a proprietary socket used only by the Fuel. Rough handling of the swivel-out hard drive tray is known to fray these cords, making them a difficult part to source.

The Fuel is the only MIPS workstation to have a USB-controller built-in. As such, USB sound cards are common alternatives to PCI for Fuel users.

Four PCI-X slots are provided, two at 66MHz and two at 33MHz.

==== Power Supply ====
The Fuel used several different power supplies over the life of the model. These units conform loosely to the WTX specification, a standard similar to ATX but more oriented towards servers. Unfortunately the Fuel is different enough that neither WTX nor ATX power supplies will not work without modification. It is believed that SGI also requested other changes for this application, including a special monitoring circuit.

=== Operating System Support ===
IRIX Versions from 6.5.17 through 6.5.30 are supported on this machine. Firewire support became functional around 6.5.27

==== Hardware Problems ====
The Fuel's cheap design has lead to many common points of failure that can destroy a system:

==== Motherboard Failures ====
Capacitor failure is common on these boards and some just mysteriously die without a cause.

==== Inadequate Ventilation ====
The CPU boards is located at the front of the case, and the memory is in front of it for airflow. This results in insufficient airflow to the CPU which can result in failures.

The same is true for the XIO2 graphics board. They are notoriously prone to failure due to either fan failure or lack of ventilation. There are no easy workarounds that exist.

==== Fans ====
The fans are tied to the environmental monitoring system and do not use the standard pinouts. This section will eventually link to a separate page discussing this.

==== Power Supply Failure ====
Fuel power supplies are variants of off-the-shelf units offered for consumer PCs. However the pinouts, if not the voltages and functions, differ even though the OEM part numbers do not. An ATX adapter is available from Kuba Tyszko but it should be noted that this should only be used with ATX power supplies that are capable of providing 30 amps on both the 3.3v and 5v rails, which is somewhat uncommon.

==== Environmental Monitoring ====
Temperature sensing on early Fuel mainboards is notoriously prone to failure, rendering the computer inoperable if environment monitoring is left on. Turning it off can allow a boot, but is not recommended.

Comments</text>
    <sha1>e3951adb8261246a231b7fa3b02fe215b91a0877</sha1>
  </revision>
  <revision>
    <id>217</id>
    <parentid>216</parentid>
    <timestamp>2025-02-16T22:21:31Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Wiki Import</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5954" xml:space="preserve">The Silicon Graphics Fuel, introduced in 2002, was intended to be a single-CPU midrange solution for those customers who did not need multiple-CPU capability, thus offering a much cheaper system compared to a baseline Tezro or top-spec single-CPU [[Octane]]. Contrary to popular belief, Fuel was not a successor to [[O2]]. SGI never made a follow-on to O2; a new system was designed (internally known as the Banana2000 or b2k) but was never developed beyond a prototype.The Fuel has a somewhat contentious reputation in the enthusiast community. In terms of form-factor and internal design, it is the most "PC-like" of the MIPS workstations, sharing much of its design with the Visual Workstation 230. Due to SGI's need to cut costs the Fuel is also likely the most error-prone workstation that SGI produced, with frequent failures of power supplies, mainboards, and environmental monitoring which most heavily plagued early revisions. The frequent failures also means a shortage of available parts, and what parts are available are expensive. So while the Fuel was meant to be a reduced-cost version of the Origin 300 architecture, it is actually the most expensive MIPS desktop to own.

=== Features ===
Fuel shares the IP35-architecture with Origin 300, Origin 350, Origin 3000, Onyx 3000 and Tezro systems.In terms of design, it is closest to a single-node Origin 300 with graphics, based on the environmental monitoring and other support chips.

The design is very similar to a standard ATX PC with the exception of the memory/CPU positions and the XIO2, used for graphics, being below the PCI-X expansion slots, meaning the board is longer and wider than a typical ATX motherboard.

==== CPU ====
The Fuel is a single processor system and can take either:

* One R14000 CPU at either 500 or 600MHz
* One R16000 CPU at 700, 800 or (rarely) 900Mhz

==== Memory ====
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Origin 300, Origin 350, and the Tezro. There are a total of four slots, organized into two banks of two slots. This results in a memory capacity from 512 MBytes to 4 Gbytes total system memory.

All DIMMS for the Fuel use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory, which remains unused in the Fuel. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

==== Graphics ====
The Fuel can have one XIO 2 graphics card, either the V10 configuration with 32MB of texture memory or the V12 with 128MB of texture memory. A dual-channel display card can be attached to offer dual head display.

==== I/O ====
Internally, the boot drive attaches to the mainboard with a 68-pin SCSI cable. Unfortunately, the connector on the mainboard itself is *not* a standard 68-pin connector and is actually a proprietary socket used only by the Fuel. Rough handling of the swivel-out hard drive tray is known to fray these cords, making them a difficult part to source.

The Fuel is the only MIPS workstation to have a USB-controller built-in. As such, USB sound cards are common alternatives to PCI for Fuel users.

Four PCI-X slots are provided, two at 66MHz and two at 33MHz.

==== Power Supply ====
The Fuel used several different power supplies over the life of the model. These units conform loosely to the WTX specification, a standard similar to ATX but more oriented towards servers. Unfortunately the Fuel is different enough that neither WTX nor ATX power supplies will not work without modification. It is believed that SGI also requested other changes for this application, including a special monitoring circuit.

=== Operating System Support ===
IRIX Versions from 6.5.17 through 6.5.30 are supported on this machine. Firewire support became functional around 6.5.27

==== Hardware Problems ====
The Fuel's cheap design has lead to many common points of failure that can destroy a system:

==== Motherboard Failures ====
Capacitor failure is common on these boards and some just mysteriously die without a cause.

==== Inadequate Ventilation ====
The CPU boards is located at the front of the case, and the memory is in front of it for airflow. This results in insufficient airflow to the CPU which can result in failures.

The same is true for the XIO2 graphics board. They are notoriously prone to failure due to either fan failure or lack of ventilation. There are no easy workarounds that exist.

==== Fans ====
The fans are tied to the environmental monitoring system and do not use the standard pinouts. This section will eventually link to a separate page discussing this.

==== Power Supply Failure ====
Fuel power supplies are variants of off-the-shelf units offered for consumer PCs. However the pinouts, if not the voltages and functions, differ even though the OEM part numbers do not. An ATX adapter is available from Kuba Tyszko but it should be noted that this should only be used with ATX power supplies that are capable of providing 30 amps on both the 3.3v and 5v rails, which is somewhat uncommon.

==== Environmental Monitoring ====
Temperature sensing on early Fuel mainboards is notoriously prone to failure, rendering the computer inoperable if environment monitoring is left on. Turning it off can allow a boot, but is not recommended.

[[Category:Hardware]]
[[Category:No-Images]]</text>
    <sha1>be8d062ae948aa3342691a0eda4e546e6af2fef5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>Prism</title>
  <ns>0</ns>
  <id>116</id>
  <revision>
    <id>219</id>
    <timestamp>2025-02-16T22:28:11Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The SGI Prism, is an [[Itanium]] based workstation sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and while visually similar to the [[Tezro]], and sharing some ancillary parts, it is a clean break in design and runs RHEL and SLES Linux. The Prism implements the IP57 processor, but follows the IP41 architecture from the earlier Altix 3000 systems.  === Features === === CPU === The Prism can take single or dual CPU configurations th..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3084" xml:space="preserve">The SGI Prism, is an [[Itanium]] based workstation sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and while visually similar to the [[Tezro]], and sharing some ancillary parts, it is a clean break in design and runs RHEL and SLES Linux. The Prism implements the IP57 processor, but follows the IP41 architecture from the earlier Altix 3000 systems. 
=== Features ===
=== CPU ===
The Prism can take single or dual CPU configurations the same as the Altix. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="2" |CPU Configurations
|-
|CPU Cache
|Speeds (GHz)
|-
|1.5MB
|1.0, 1.4
|-
|3MB
|1.3, 1.4, 1.6
|-
|4MB
|1.4, 1.5
|-
|6MB
|1.5, 1.6
|-
|9MB
|1.6
|}

=== Memory ===
Like other first-generation Altix systems, the Prism uses registered DDR DIMMs with ECC, rated at 266MHz or faster, which are commonly referred to as PC2100, PC2700, etc. Memory is organized in three banks of four DIMMs each, or twelve slots total, providing up to 24GB of RAM total per base module. DIMMs of 512MB, 1GB, and 2GB are officially supported; it is unclear as of this writing if 4GB parts will work.

=== I/O ===
The IO9 controller supports Ultra160 SCSI devices and includes an externally-accessible VHDCI port, while the IO10 controller supports SATA devices and includes a high density serial connector. Both controllers include a separate IDE interface to support optical drives.

Either IO controller provides one 1000baseT Ethernet interface. Three PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more. The BaseIO card must be installed in the bottom slot.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== Storage ===
The Prism has a front bay for two 3.5" drives. It uses proprietary sleds for this purpose.

The Origin/Onyx 350, Prism, Altix 350, and Altix 450/4x00 all use the same drive carriers. These are standard parts used by a number of manufacturers, notably Intel's SC5200, SRSH4, SR1300/2300, and SR1400/2400 and Sun's v60x and v65x servers.

The units carry "Assy A65278-00x" on a sticker, where the "-00x" may end in any digit though "-005" seems common. This assembly number can be useful when searching for parts in the Internet. According to SR1300/SR2300 support documents at intel.com, the Intel accessory part number for the drive carrier is FXX2DRVCARBLK, UPC code "7 35858 14621 0" and "MM #" 835853. However note that there is some indication that Intel may recycle these accessory part numbers in the FXX- form between different models.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator called an L3 controller.

=== Operating System Support ===
The system can run Microsoft Windows up to Server 2008 R2 (Itanium Edition) and GNU/Linux RHEL and SLES up to versions 5 and 9 respectively.

[[Category:Hardware]]</text>
    <sha1>a55e06d1c796da90f0c671bfe3b39f8d33a5200f</sha1>
  </revision>
  <revision>
    <id>220</id>
    <parentid>219</parentid>
    <timestamp>2025-02-16T22:28:32Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3107" xml:space="preserve">The SGI Prism, is an [[Itanium]] based workstation sold by Silicon Graphics from 2005 to 2007. This system uses Itanium 2-based processors and while visually similar to the [[Tezro]], and sharing some ancillary parts, it is a clean break in design and runs RHEL and SLES Linux. The Prism implements the IP57 processor, but follows the IP41 architecture from the earlier Altix 3000 systems. 
=== Features ===
=== CPU ===
The Prism can take single or dual CPU configurations the same as the Altix. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="2" |CPU Configurations
|-
|CPU Cache
|Speeds (GHz)
|-
|1.5MB
|1.0, 1.4
|-
|3MB
|1.3, 1.4, 1.6
|-
|4MB
|1.4, 1.5
|-
|6MB
|1.5, 1.6
|-
|9MB
|1.6
|}

=== Memory ===
Like other first-generation Altix systems, the Prism uses registered DDR DIMMs with ECC, rated at 266MHz or faster, which are commonly referred to as PC2100, PC2700, etc. Memory is organized in three banks of four DIMMs each, or twelve slots total, providing up to 24GB of RAM total per base module. DIMMs of 512MB, 1GB, and 2GB are officially supported; it is unclear as of this writing if 4GB parts will work.

=== I/O ===
The IO9 controller supports Ultra160 SCSI devices and includes an externally-accessible VHDCI port, while the IO10 controller supports SATA devices and includes a high density serial connector. Both controllers include a separate IDE interface to support optical drives.

Either IO controller provides one 1000baseT Ethernet interface. Three PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more. The BaseIO card must be installed in the bottom slot.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== Storage ===
The Prism has a front bay for two 3.5" drives. It uses proprietary sleds for this purpose.

The Origin/Onyx 350, Prism, Altix 350, and Altix 450/4x00 all use the same drive carriers. These are standard parts used by a number of manufacturers, notably Intel's SC5200, SRSH4, SR1300/2300, and SR1400/2400 and Sun's v60x and v65x servers.

The units carry "Assy A65278-00x" on a sticker, where the "-00x" may end in any digit though "-005" seems common. This assembly number can be useful when searching for parts in the Internet. According to SR1300/SR2300 support documents at intel.com, the Intel accessory part number for the drive carrier is FXX2DRVCARBLK, UPC code "7 35858 14621 0" and "MM #" 835853. However note that there is some indication that Intel may recycle these accessory part numbers in the FXX- form between different models.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator called an L3 controller.

=== Operating System Support ===
The system can run Microsoft Windows up to Server 2008 R2 (Itanium Edition) and GNU/Linux RHEL and SLES up to versions 5 and 9 respectively.

[[Category:Hardware]]
[[Category:No-Images]]</text>
    <sha1>cb2d0bc55204b6297b6d9b884a701f0f84b01f23</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>Power Series</title>
  <ns>0</ns>
  <id>117</id>
  <revision>
    <id>221</id>
    <timestamp>2025-02-16T22:30:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The PowerSeries systems are the first multiprocessor computers made by Silicon Graphics and were typically shipped in a single or twin tower case. PowerSeries systems were first produced in twin tower shaped chassis, and later on single tower chassis was introduced. The high-end systems (more than 4 CPUs) were shipped in a "refrigerator-style" rack due to space limitations in the desk-side cases.  [[Category:Hardware]] [[Category:Stubs]] [[Category:No-Images]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="464" xml:space="preserve">The PowerSeries systems are the first multiprocessor computers made by Silicon Graphics and were typically shipped in a single or twin tower case. PowerSeries systems were first produced in twin tower shaped chassis, and later on single tower chassis was introduced. The high-end systems (more than 4 CPUs) were shipped in a "refrigerator-style" rack due to space limitations in the desk-side cases.

[[Category:Hardware]]
[[Category:Stubs]]
[[Category:No-Images]]</text>
    <sha1>eccd9c212bea0d28d72e23d2952ebd93d663b1fd</sha1>
  </revision>
  <revision>
    <id>230</id>
    <parentid>221</parentid>
    <timestamp>2025-02-16T22:44:08Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="523" xml:space="preserve">The PowerSeries systems are the first multiprocessor computers made by Silicon Graphics and were typically shipped in a single or twin tower case. PowerSeries systems were first produced in twin tower shaped chassis, and later on single tower chassis was introduced. The high-end systems (more than 4 CPUs) were shipped in a "refrigerator-style" rack due to space limitations in the desk-side cases. 

Some resemble the earlier [[Professional IRIS]] systems.

[[Category:Hardware]]
[[Category:Stubs]]
[[Category:No-Images]]</text>
    <sha1>fd3d316f1ad4a832eec02ee12514a98ecb4beeb4</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>GL2-3.x</title>
  <ns>0</ns>
  <id>118</id>
  <revision>
    <id>223</id>
    <timestamp>2025-02-16T22:37:54Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "GL2-3.x was the final series released for the Motorola 68000-based [[68k-based SGIs (IRIS Series)|IRIS Series]] of terminals and workstations. GL2 uses the [[MEX]] windowing system. Significant improvements were made over the 2.x series.  === Changes from 2.x ===  * System V Shared Memory API * 4.3BSD based TCP/IP stack\ * NFSv1 and yp/NIS"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="341" xml:space="preserve">GL2-3.x was the final series released for the Motorola 68000-based [[68k-based SGIs (IRIS Series)|IRIS Series]] of terminals and workstations. GL2 uses the [[MEX]] windowing system. Significant improvements were made over the 2.x series.

=== Changes from 2.x ===

* System V Shared Memory API
* 4.3BSD based TCP/IP stack\
* NFSv1 and yp/NIS</text>
    <sha1>e652f7b1e642e6a2c5008db98b23b9f84d69b19e</sha1>
  </revision>
  <revision>
    <id>227</id>
    <parentid>223</parentid>
    <timestamp>2025-02-16T22:42:44Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="425" xml:space="preserve">GL2-3.x was the final series released for the Motorola 68000-based [[68k-based SGIs (IRIS Series)|IRIS Series]] of terminals and workstations. GL2 uses the [[MEX]] windowing system. Significant improvements were made over the 2.x series.

=== Changes from 2.x ===

* System V Shared Memory API
* 4.3BSD based TCP/IP stack
* NFSv1 and yp/NIS

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]
[[Category:68k]]</text>
    <sha1>57713478dcd55aac96fd48e480ec8a85e22ada49</sha1>
  </revision>
  <revision>
    <id>240</id>
    <parentid>227</parentid>
    <timestamp>2025-02-17T02:19:15Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="485" xml:space="preserve">GL2-3.x was the final series released for the Motorola 68000-based [[68k-based SGIs (IRIS Series)|IRIS Series]] of terminals and workstations. GL2 uses the [[MEX]] windowing system. Significant improvements were made over the 2.x series.

=== Changes from 2.x ===

* System V Shared Memory API
* [[File:MEX.png|thumb|MEX Demonstration on a 68k-based IRIS]]4.3BSD based TCP/IP stack
* NFSv1 and yp/NIS

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]
[[Category:68k]]</text>
    <sha1>ca18a60747ec9655d3975ed0eeb08474afc2b8d2</sha1>
  </revision>
  <revision>
    <id>241</id>
    <parentid>240</parentid>
    <timestamp>2025-02-17T02:19:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="462" xml:space="preserve">GL2-3.x was the final series released for the Motorola 68000-based [[68k-based SGIs (IRIS Series)|IRIS Series]] of terminals and workstations. GL2 uses the [[MEX]] windowing system. Significant improvements were made over the 2.x series.

=== Changes from 2.x ===

* System V Shared Memory API
* [[File:MEX.png|thumb|MEX Demonstration on a 68k-based IRIS]]4.3BSD based TCP/IP stack
* NFSv1 and yp/NIS

[[Category:OS-Versions]]
[[Category:Stubs]]
[[Category:68k]]</text>
    <sha1>b108026531f02fad1e0f406e58490d87c66659e3</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>GL2-2.x</title>
  <ns>0</ns>
  <id>119</id>
  <revision>
    <id>224</id>
    <timestamp>2025-02-16T22:40:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "GL2-2.x was released in 1986 for the IRIS 1000 and 2000 68000-based SGI terminals and workstations. It is the origin of the [[EFS]] system which replaced the AT&amp;T UFS implementation."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="182" xml:space="preserve">GL2-2.x was released in 1986 for the IRIS 1000 and 2000 68000-based SGI terminals and workstations. It is the origin of the [[EFS]] system which replaced the AT&amp;T UFS implementation.</text>
    <sha1>a76c41b17a6038d9d97edf26cdb376bdf5f8c3fc</sha1>
  </revision>
  <revision>
    <id>228</id>
    <parentid>224</parentid>
    <timestamp>2025-02-16T22:43:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="267" xml:space="preserve">GL2-2.x was released in 1986 for the IRIS 1000 and 2000 68000-based SGI terminals and workstations. It is the origin of the [[EFS]] system which replaced the AT&amp;T UFS implementation.

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]
[[Category:68k]]</text>
    <sha1>ec2caf0af841de01a66220fa3d9c352bbec54e17</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>Style Guide</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>225</id>
    <parentid>6</parentid>
    <timestamp>2025-02-16T22:40:57Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2078" xml:space="preserve">In the interest of basic quality standards, TechPubs maintains this page to ensure that all of its editors follow basic guidelines.

=== Formatting ===
By far this is the most imperative section to read. Please read for our standards for page formatting:

- Each subsection must use a Subheading 1 headline.

-  Use &lt;nowiki&gt;&lt;code&gt;&lt;/code&gt;&lt;/nowiki&gt; around single lines of text, use &lt;nowiki&gt;&lt;pre&gt; &lt;/pre&gt;&lt;/nowiki&gt; for blocks

==== Shell Commands ====
As previously stated, use the code tag for shell commands. The format of the command should be as follows:

&lt;code&gt;# command &lt;generic argument&gt;&lt;/code&gt;

For root commands. For user-level commands, use the % sign like this:

&lt;code&gt;% command &lt;generic argument&gt;&lt;/code&gt;

Avoid bashisms or providing bash scripts. If at all possible, write scripts in korn/C shell and use the appropriate shebang. Bash is not a default shell in IRIX, nor is it preinstalled and the sooner bash habits can be unlearned, the better.

=== Categories ===
Categories

=== Tone, Writing Style, and Point of View ===
When possible, avoid use of pronouns of any kind unless talking about a specific individual or user. Do not address the reader as "you" and avoid use of "we, I, they, the user, the reader" etc. in writing. If there is a need to refer to someone, use "one" as in "One may wish to heed this section of the style guide.".

When a person's sex is indeterminate, i,e. talking about a user, refer to the person using the person's username. Do not use 'they', 'he' or 'she' if the user's sex is unknown.

All articles should be written with a neutral, professional writing style that uses necessary technical jargon. The audience to keep in mind is a UNIX user with command line experience.

=== Edit Wars ===
Edit warring can happen to any wiki, including this one. The appropriate response in this is to contact Raion on the IRIXNet forums immediately in the case of any edit warring. Admins are to adhere to the following rules in judging the appropriate action:

* This Style Guide
* His/her own judgment
* The author of the article (if a Tutorial)</text>
    <sha1>91d83886592ca8a67a16d9145c7f2eabcb499a4a</sha1>
  </revision>
  <revision>
    <id>226</id>
    <parentid>225</parentid>
    <timestamp>2025-02-16T22:41:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2174" xml:space="preserve">In the interest of basic quality standards, TechPubs maintains this page to ensure that all of its editors follow basic guidelines.

=== Formatting ===
By far this is the most imperative section to read. Please read for our standards for page formatting:

- Each subsection must use a Subheading 1 headline.

-  Use &lt;nowiki&gt;&lt;code&gt;&lt;/code&gt;&lt;/nowiki&gt; around single lines of text, use &lt;nowiki&gt;&lt;pre&gt; &lt;/pre&gt;&lt;/nowiki&gt; for blocks

==== Shell Commands ====
As previously stated, use the code tag for shell commands. The format of the command should be as follows:

&lt;code&gt;# command &lt;generic argument&gt;&lt;/code&gt;

For root commands. For user-level commands, use the % sign like this:

&lt;code&gt;% command &lt;generic argument&gt;&lt;/code&gt;

Avoid bashisms or providing bash scripts. If at all possible, write scripts in korn/C shell and use the appropriate shebang. Bash is not a default shell in IRIX, nor is it preinstalled and the sooner bash habits can be unlearned, the better.

=== Categories ===
Categories may not have spaces in them. Use hyphens to space out words. Each page should have a category. 

=== Tone, Writing Style, and Point of View ===
When possible, avoid use of pronouns of any kind unless talking about a specific individual or user. Do not address the reader as "you" and avoid use of "we, I, they, the user, the reader" etc. in writing. If there is a need to refer to someone, use "one" as in "One may wish to heed this section of the style guide.".

When a person's sex is indeterminate, i,e. talking about a user, refer to the person using the person's username. Do not use 'they', 'he' or 'she' if the user's sex is unknown.

All articles should be written with a neutral, professional writing style that uses necessary technical jargon. The audience to keep in mind is a UNIX user with command line experience.

=== Edit Wars ===
Edit warring can happen to any wiki, including this one. The appropriate response in this is to contact Raion on the IRIXNet forums immediately in the case of any edit warring. Admins are to adhere to the following rules in judging the appropriate action:

* This Style Guide
* His/her own judgment
* The author of the article (if a Tutorial)</text>
    <sha1>a0779ed1985dfdc8037f748378eb120ba68db8f9</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>File:Irix-4.0.1-img1.gif</title>
  <ns>6</ns>
  <id>120</id>
  <revision>
    <id>231</id>
    <timestamp>2025-02-17T02:04:37Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="63" xml:space="preserve">IRIX 4.0.1 Desktop with IRIS Showcase. Courtesy of sgistuff.net</text>
    <sha1>bd22edb67a44d4881131d19d0e1a6da782591730</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>File:4d1-3.3-Demos.gif</title>
  <ns>6</ns>
  <id>121</id>
  <revision>
    <id>233</id>
    <timestamp>2025-02-17T02:06:27Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">Demos of 4D1 3.3</text>
    <sha1>5f0de9d5c589a0995bc5393ae45218d0aa591494</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>File:4d1-3.3-term.gif</title>
  <ns>6</ns>
  <id>122</id>
  <revision>
    <id>234</id>
    <timestamp>2025-02-17T02:07:35Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">4D1 wsh terminal</text>
    <sha1>d1fe5d27bc9ad3492a631196b346478c7c955c07</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>File:4D1 4Sight.gif</title>
  <ns>6</ns>
  <id>123</id>
  <revision>
    <id>236</id>
    <timestamp>2025-02-17T02:08:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11" xml:space="preserve">4Sight Demo</text>
    <sha1>ea884b37197ee65b3b720909699f4234e0920cdc</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>4Sight</title>
  <ns>0</ns>
  <id>124</id>
  <revision>
    <id>237</id>
    <timestamp>2025-02-17T02:12:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "4Sight is the windowing system used by 4D1 (the immediate predecessor of IRIX). It is based on the NeWS system produced by Sun Microsystems. It is a stacking windowing system with full IRISGL-type graphical acceleration and effects.  [[File:4D1 4Sight.gif|thumb|4D1 3.3 uses the 4Sight windowing system]] IRIX 4.x and up uses XSGI, an X11-based windowing system, instead of 4Sight as by this point NeWS was seen as passe due to its slower speed, poor market acceptance and th..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="565" xml:space="preserve">4Sight is the windowing system used by 4D1 (the immediate predecessor of IRIX). It is based on the NeWS system produced by Sun Microsystems. It is a stacking windowing system with full IRISGL-type graphical acceleration and effects. 
[[File:4D1 4Sight.gif|thumb|4D1 3.3 uses the 4Sight windowing system]]
IRIX 4.x and up uses XSGI, an X11-based windowing system, instead of 4Sight as by this point NeWS was seen as passe due to its slower speed, poor market acceptance and the fact that it required PostScript royalties.


[[Category:Stubs]]
[[Category:Subsystems]]</text>
    <sha1>db0baa8417dd567c178eae7542b3ad1ac31d73da</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>File:MEX.png</title>
  <ns>6</ns>
  <id>125</id>
  <revision>
    <id>239</id>
    <timestamp>2025-02-17T02:18:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="40" xml:space="preserve">MEX demonstration on an IRIS 68k machine</text>
    <sha1>9ad10986bb52232fe0aff79575f8dd6b5ff13fca</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>MEX</title>
  <ns>0</ns>
  <id>126</id>
  <revision>
    <id>242</id>
    <timestamp>2025-02-17T02:20:22Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "MEX is a GL accelerated, stacking window system for GL2, one of two predecessors of the 4D1 operating system,  [[File:MEX.png|thumb|MEX Demonstration on a 68k-based IRIS]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="171" xml:space="preserve">MEX is a GL accelerated, stacking window system for GL2, one of two predecessors of the 4D1 operating system, 
[[File:MEX.png|thumb|MEX Demonstration on a 68k-based IRIS]]</text>
    <sha1>be73e48ea7ef4e1027105d47677a26a8724394de</sha1>
  </revision>
  <revision>
    <id>243</id>
    <parentid>242</parentid>
    <timestamp>2025-02-17T02:20:52Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="215" xml:space="preserve">MEX is a GL accelerated, stacking window system for GL2, one of two predecessors of the 4D1 operating system, 
[[File:MEX.png|thumb|MEX Demonstration on a 68k-based IRIS]]

[[Category:Subsystems]]
[[Category:Stubs]]</text>
    <sha1>be802f08cf4c68380595f1f28cb042e57db95c73</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>User talk:Raion</title>
  <ns>3</ns>
  <id>127</id>
  <revision>
    <id>246</id>
    <timestamp>2025-02-19T01:17:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Nekoware drafts</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1828" xml:space="preserve">Nekoware Draft.

Nekoware is a community project targeting IRIX 6.5.21 or later (most commonly .22 and .30) MIPS IV systems. 

It is a high performance, well-optimized group of LTS supported software. Each package has a maintainer. 

Nekoware is released on a quarterly basis, with the newest iteration of it starting at 2025-Q2. 

Each quarter, the entire base release is rebuilt. Not all packages are turned over, but many are. 

Building:

This is the official N32 Nekoware build environment standard:

setenv CC c99
setenv CXX CC
setenv CFLAGS '-O2 -mips4 -TARG:proc=r10000'
setenv CXXFLAGS '-O2 -mips4 -TARG:proc=r10000'
setenv CPPFLAGS '-I/usr/nekoware/include -I/usr/include'
setenv LDFLAGS '-L/usr/nekoware/lib32 -L/usr/lib32 -Wl,-rpath -Wl,/usr/nekoware/lib32'
setenv PKG_CONFIG '/usr/nekoware/bin/pkgconfig'
setenv PKG_CONFIG_PATH '/usr/nekoware/lib32/pkgconfig'

Additional opts can be added as necessary as well as ENV vars. 

GCC Policy:

Nekoware does primarily build software with MIPSPro, but in light of GCC advancements and the fact it's a decent compiler, it is permitted for software. The following caveats for making GCC packages apply:

GCC does not play nice with the C++ of MIPSPro. The C++ ABIs are dissimilar so any projects making use of C++ must reduplicate their C++ dependencies at minimum. 

Paths for GCC libs and includes are:

/usr/nekoware/gcc-include
/usr/nekoware/gcc-lib32

GNOME, KDE and FreeDesktop projects Policies:
We wish to avoid integrating security and bloat issues into IRIX where possible. As such, we do not permit most GNOME and KDE dependencies, and even less FreeDesktop libs. This can include:

Policykit
Consolekit
dbus/messagebus
GNOME bonobo/KDE DCOP/CORBA

Such systems are better suited for the likes of SGUG-RSE. 

Otherwise, go wild. We accept any packages otherwise.</text>
    <sha1>e7cb79bf8dad801adff98a7d0d431dfc65902b71</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>Vintage Computer Festival</title>
  <ns>0</ns>
  <id>106</id>
  <revision>
    <id>247</id>
    <parentid>159</parentid>
    <timestamp>2025-02-20T18:00:22Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="666" xml:space="preserve">VCF is a series of festivals and swap meets hosted around the world.

=== Events and Their Locations ===
VCF has several different meets located in different parts of North America:

* VCF East: Wall Township, NJ
* VCF West: Mountain View, CA
* VCF Montreal: Montreal, Quebec, Canada,
* VCF SoCal: Orange, CA
* VCF Southwest: Dallas, TX
* VCF Southeast: Atlanta, GA
* VCF Midwest: Schaumburg, IL
* VCF Zurich: Zurich, Switzerland

=== Reasons to Visit ===
SGI users all over the world come to these events, they are a small but somewhat tight knit group. It's also excellent for professional networking. 
[[Category:Events]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>989909c8ed82ab9b0578cc5bf7a4ca2cbf944955</sha1>
  </revision>
  <revision>
    <id>249</id>
    <parentid>247</parentid>
    <timestamp>2025-02-20T18:02:08Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>linked</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="706" xml:space="preserve">VCF is a series of festivals and swap meets hosted around the world.

For more info, visit https://vcfed.org

=== Events and Their Locations ===
VCF has several different meets located in different parts of North America:

* VCF East: Wall Township, NJ
* VCF West: Mountain View, CA
* VCF Montreal: Montreal, Quebec, Canada,
* VCF SoCal: Orange, CA
* VCF Southwest: Dallas, TX
* VCF Southeast: Atlanta, GA
* VCF Midwest: Schaumburg, IL
* VCF Zurich: Zurich, Switzerland

=== Reasons to Visit ===
SGI users all over the world come to these events, they are a small but somewhat tight knit group. It's also excellent for professional networking. 
[[Category:Events]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>8c67d71b8fdf8d1d844bc0ec32ae0bd4713c0b31</sha1>
  </revision>
  <revision>
    <id>250</id>
    <parentid>249</parentid>
    <timestamp>2025-02-20T18:02:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="687" xml:space="preserve">VCF is a series of festivals and swap meets hosted around the world.

For more info, visit https://vcfed.org

=== Events and Their Locations ===
VCF has several different meets located in different parts of North America:

* VCF East: Wall Township, NJ
* VCF West: Mountain View, CA
* VCF Montreal: Montreal, Quebec, Canada,
* VCF SoCal: Orange, CA
* VCF Southwest: Dallas, TX
* VCF Southeast: Atlanta, GA
* VCF Midwest: Schaumburg, IL
* VCF Zurich: Zurich, Switzerland

=== Reasons to Visit ===
SGI users all over the world come to these events, they are a small but somewhat tight knit group. It's also excellent for professional networking. 
[[Category:Events]]
[[Category:No-Images]]</text>
    <sha1>0d332e8d55110901951f9380a6f42d9732dad325</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>SGUG</title>
  <ns>0</ns>
  <id>105</id>
  <revision>
    <id>251</id>
    <parentid>162</parentid>
    <timestamp>2025-02-20T18:11:18Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="678" xml:space="preserve">Silicon Graphics User Group is a community for SGI discussion that has a forum and chat system. It is one of two post [[Nekochan.net]] groups, the other being [[IRIXNet]]. 

=== Contents ===
SGUG is a forum and discord system. The forums use XenForo2 and boast a userbase comparable [[IRIXNet]], it also posesses an IRC/Discord hybrid chat system. 

=== History ===
SGUG was founded in 2019 as an offshoot of IRIXNet. While community disagreements have caused a rocky history, these were mostly resolved by late 2024 and reconciliation is ongoing. SGUG is the creator of the free software project [[SGUG RSE]]. 
[[Category:Communities]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>20414ed660b94e7a9a6c53a4e8bab4bf2e540f81</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-16 21:45:20+00|203">
  <title>IRIXNet</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>252</id>
    <parentid>165</parentid>
    <timestamp>2025-02-20T18:13:31Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1188" xml:space="preserve">IRIXNet, short for IRIX Network, is a Silicon Graphics-focused website, forum and archive of former hobbyist sites that was founded in 2017 by Raion (Kaz Kuroi) and Praetor (George). It was founded with the express purpose of providing a secondary Silicon Graphics site separate to [[Nekochan.net]] due to recent concerns of downtime at the time, and to facilitate open sales of commercial software. 

=== Contents ===
IRIXNet has an archive, file servers, gallery and forums. It exists as one of two English language SGI-related sites offering forums, the other being [[SGUG]].

=== History ===
IRIXNet was founded in 2017 to serve as a feeder site for Nekochan.net. However on May 21, 2018 Nekochan went offline for the final time and IRIXNet was pushed into a role of being the primary community. [[SGUG]] was founded a year later in 2019 for the same purpose. 

=== Association with TechPubs ===
TechPubs is owned by Raion, who also owns IRIXNet, but the purpose of Techpubs is far more focused on documentation and to serve as an SEO-friendly SGI instructional website. It does not inherit the moderation team or policies of IRIXNet.


[[Category:Communities]]
[[Category:No-Images]]</text>
    <sha1>3a9e0ccc081898188623dad1d7270ac3823a7b0b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>File:Sgug mainpage.jpg</title>
  <ns>6</ns>
  <id>128</id>
  <revision>
    <id>253</id>
    <timestamp>2025-02-20T18:24:57Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="26" xml:space="preserve">SGUG's mainpage as of 2025</text>
    <sha1>b4445e009c1e78d10250dc841a0ed99997e8ba80</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>SGUG</title>
  <ns>0</ns>
  <id>105</id>
  <revision>
    <id>254</id>
    <parentid>251</parentid>
    <timestamp>2025-02-20T18:26:00Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="703" xml:space="preserve">Silicon Graphics User Group is a community for SGI discussion that has a forum and chat system. It is one of two post [[Nekochan.net]] groups, the other being [[IRIXNet]]. 
[[File:Sgug mainpage.jpg|thumb|SGUG's mainpage captured Feb 2025]]

=== Contents ===
SGUG is a forum and discord system. The forums use XenForo2 and boast a userbase comparable [[IRIXNet]], it also posesses an IRC/Discord hybrid chat system. 

=== History ===
SGUG was founded in 2019 as an offshoot of IRIXNet. While community disagreements have caused a rocky history, these were mostly resolved by late 2024 and reconciliation is ongoing. SGUG is the creator of the free software project [[SGUG RSE]]. 
[[Category:Communities]]</text>
    <sha1>0d1266eaf8e52207aef02cb6dc64f166dbf48221</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>File:Irixnet mainpage.jpg</title>
  <ns>6</ns>
  <id>129</id>
  <revision>
    <id>255</id>
    <timestamp>2025-02-20T18:27:02Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39" xml:space="preserve">Main page of IRIXNet, captured Feb 2025</text>
    <sha1>7aa1499696adbae84ff69bfff5f7ca9d33dbae9f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>IRIXNet</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>256</id>
    <parentid>252</parentid>
    <timestamp>2025-02-20T18:27:22Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1264" xml:space="preserve">[[File:Irixnet mainpage.jpg|thumb|Main page of IRIXNet, captured Feb 2025]]
IRIXNet, short for IRIX Network, is a Silicon Graphics-focused website, forum and archive of former hobbyist sites that was founded in 2017 by Raion (Kaz Kuroi) and Praetor (George). It was founded with the express purpose of providing a secondary Silicon Graphics site separate to [[Nekochan.net]] due to recent concerns of downtime at the time, and to facilitate open sales of commercial software. 

=== Contents ===
IRIXNet has an archive, file servers, gallery and forums. It exists as one of two English language SGI-related sites offering forums, the other being [[SGUG]].

=== History ===
IRIXNet was founded in 2017 to serve as a feeder site for Nekochan.net. However on May 21, 2018 Nekochan went offline for the final time and IRIXNet was pushed into a role of being the primary community. [[SGUG]] was founded a year later in 2019 for the same purpose. 

=== Association with TechPubs ===
TechPubs is owned by Raion, who also owns IRIXNet, but the purpose of Techpubs is far more focused on documentation and to serve as an SEO-friendly SGI instructional website. It does not inherit the moderation team or policies of IRIXNet.


[[Category:Communities]]
[[Category:No-Images]]</text>
    <sha1>62bb4fe6b2f416861938ed7a4e40285a1c39b888</sha1>
  </revision>
  <revision>
    <id>257</id>
    <parentid>256</parentid>
    <timestamp>2025-02-20T18:27:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1241" xml:space="preserve">[[File:Irixnet mainpage.jpg|thumb|Main page of IRIXNet, captured Feb 2025]]
IRIXNet, short for IRIX Network, is a Silicon Graphics-focused website, forum and archive of former hobbyist sites that was founded in 2017 by Raion (Kaz Kuroi) and Praetor (George). It was founded with the express purpose of providing a secondary Silicon Graphics site separate to [[Nekochan.net]] due to recent concerns of downtime at the time, and to facilitate open sales of commercial software. 

=== Contents ===
IRIXNet has an archive, file servers, gallery and forums. It exists as one of two English language SGI-related sites offering forums, the other being [[SGUG]].

=== History ===
IRIXNet was founded in 2017 to serve as a feeder site for Nekochan.net. However on May 21, 2018 Nekochan went offline for the final time and IRIXNet was pushed into a role of being the primary community. [[SGUG]] was founded a year later in 2019 for the same purpose. 

=== Association with TechPubs ===
TechPubs is owned by Raion, who also owns IRIXNet, but the purpose of Techpubs is far more focused on documentation and to serve as an SEO-friendly SGI instructional website. It does not inherit the moderation team or policies of IRIXNet.


[[Category:Communities]]</text>
    <sha1>b5ac8fe57323a6556d5abed3a194050993680b38</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>258</id>
    <parentid>222</parentid>
    <timestamp>2025-02-20T18:44:36Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3831" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>942a9f95f54f54b424973a04d91aa925401c343b</sha1>
  </revision>
  <revision>
    <id>289</id>
    <parentid>258</parentid>
    <timestamp>2025-02-23T05:24:06Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3876" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>fb9377a1512ef0c087d672431065a2f1670c8023</sha1>
  </revision>
  <revision>
    <id>293</id>
    <parentid>289</parentid>
    <timestamp>2025-02-23T05:29:14Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Peripherals */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3912" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[Tape Drives|Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>eb6c1c59b5cdab56a05835d002d60b060287cc41</sha1>
  </revision>
  <revision>
    <id>294</id>
    <parentid>293</parentid>
    <timestamp>2025-02-23T05:29:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Peripherals */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3900" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>c2cc921421afd8da99805ee8b8cd02d2041603c4</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>NFS</title>
  <ns>0</ns>
  <id>32</id>
  <revision>
    <id>259</id>
    <parentid>40</parentid>
    <timestamp>2025-02-20T18:45:42Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2589" xml:space="preserve">NFS or Networked File System is a protocol used to share filesystems over a network. IRIX includes support for NFSv2 and NFSv3.

=== Hosting NFS ===
'''NFSv2 and NFSv3 have known security problems and exploits. It's highly advised to use a proper firewall and configuration.'''

NFS can be hosted from IRIX, BSD, Solaris/illumos, Linux or even some versions of macOS and still retain compatibility to IRIX. This page documents related issues with NFSv3/2 and the various quirks to get it working on each host OS.

=== Recommended Hosts ===
The easiest hosts to get working with IRIX are, in no particular order:

* illumos/Solaris
* FreeBSD
* NetBSD
* IRIX 6.5.22 or higher
* Windows 10 Pro or Enterprise

=== Not Recommended ===
These hosts have a number of server and implementation issues with NFSv3, if there are tricks unheard of yet to getting them working please feel free to add tricks below:

* Linux: rpcbind in Linux is buggy, and the nfsd module usually gets interfered with by SELinux, systemd and other modern Linuxisms.
* macOS: The most recent versions do not appear to have proper NFSv3 support for hosting, though NFSv3 connections do appear to work.

=== Guides ===

==== FreeBSD ====
FreeBSD supports NFSv3 for IRIX easily.

'''Enabling Services'''

The following lines must be added to the /etc/rc.conf file:&lt;pre&gt;
rpcbind_enable="YES"

nfs_server_enable="YES"

mountd_enable="YES"

mountd_flags="-r -p 735"
&lt;/pre&gt;Now start the services:

&lt;code&gt;# service rpcbind start; service nfsd start; service mountd reload&lt;/code&gt;

'''Exporting'''

On ZFS, do not use /etc/exports. Instead, use:

&lt;code&gt;zfs sharenfs="-network 10.0.0.0 -mask 255.255.255.0" tank/protected&lt;/code&gt;

This will share the tank/protected dataset on LAN addresses 10.0.0.0/24

Further examples will include PF firewall rules to ensure spoofed/hostile traffic cannot compromise NFS.

==== Linux (Ubuntu) ====
Thanks to Larbob/lbdm for this guide.

'''Preparation'''

Install the NFS subsystem:

&lt;code&gt;sudo apt install nfs-kernel-server&lt;/code&gt;

Make an NFS share directory:

&lt;code&gt;sudo mkdir -p /srv/nfs&lt;/code&gt;

Set up /etc/exports with something like this:

&lt;code&gt;/srv/nfs 192.168.0.0/24(rw,sync,no_subtree_check,no_root_squash)&lt;/code&gt;

Edit /etc/default/nfs-kernel-server's RPCMOUNTDOPTS section to add --no-nfs-version 4

'''Finishing Touches'''&lt;pre&gt;
sudo exportfs -ra

sudo systemctl restart nfs-config

sudo systemctl restart nfs-kernel-server
&lt;/pre&gt;This will provide a setup to allow anyone with uid 0 to write as root. Please be careful if deciding this.

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>ba35eee9adcc1d189088330511949abe36dfb43d</sha1>
  </revision>
  <revision>
    <id>268</id>
    <parentid>259</parentid>
    <timestamp>2025-02-20T22:42:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2597" xml:space="preserve">NFS or Networked File System is a protocol used to share filesystems over a network. [[IRIX 6.5]] includes support for NFSv2 and NFSv3.

=== Hosting NFS ===
'''NFSv2 and NFSv3 have known security problems and exploits. It's highly advised to use a proper firewall and configuration.'''

NFS can be hosted from IRIX, BSD, Solaris/illumos, Linux or even some versions of macOS and still retain compatibility to IRIX. This page documents related issues with NFSv3/2 and the various quirks to get it working on each host OS.

=== Recommended Hosts ===
The easiest hosts to get working with IRIX are, in no particular order:

* illumos/Solaris
* FreeBSD
* NetBSD
* IRIX 6.5.22 or higher
* Windows 10 Pro or Enterprise

=== Not Recommended ===
These hosts have a number of server and implementation issues with NFSv3, if there are tricks unheard of yet to getting them working please feel free to add tricks below:

* Linux: rpcbind in Linux is buggy, and the nfsd module usually gets interfered with by SELinux, systemd and other modern Linuxisms.
* macOS: The most recent versions do not appear to have proper NFSv3 support for hosting, though NFSv3 connections do appear to work.

=== Guides ===

==== FreeBSD ====
FreeBSD supports NFSv3 for IRIX easily.

'''Enabling Services'''

The following lines must be added to the /etc/rc.conf file:&lt;pre&gt;
rpcbind_enable="YES"

nfs_server_enable="YES"

mountd_enable="YES"

mountd_flags="-r -p 735"
&lt;/pre&gt;Now start the services:

&lt;code&gt;# service rpcbind start; service nfsd start; service mountd reload&lt;/code&gt;

'''Exporting'''

On ZFS, do not use /etc/exports. Instead, use:

&lt;code&gt;zfs sharenfs="-network 10.0.0.0 -mask 255.255.255.0" tank/protected&lt;/code&gt;

This will share the tank/protected dataset on LAN addresses 10.0.0.0/24

Further examples will include PF firewall rules to ensure spoofed/hostile traffic cannot compromise NFS.

==== Linux (Ubuntu) ====
Thanks to Larbob/lbdm for this guide.

'''Preparation'''

Install the NFS subsystem:

&lt;code&gt;sudo apt install nfs-kernel-server&lt;/code&gt;

Make an NFS share directory:

&lt;code&gt;sudo mkdir -p /srv/nfs&lt;/code&gt;

Set up /etc/exports with something like this:

&lt;code&gt;/srv/nfs 192.168.0.0/24(rw,sync,no_subtree_check,no_root_squash)&lt;/code&gt;

Edit /etc/default/nfs-kernel-server's RPCMOUNTDOPTS section to add --no-nfs-version 4

'''Finishing Touches'''&lt;pre&gt;
sudo exportfs -ra

sudo systemctl restart nfs-config

sudo systemctl restart nfs-kernel-server
&lt;/pre&gt;This will provide a setup to allow anyone with uid 0 to write as root. Please be careful if deciding this.

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>4bc9776afba7f56f426657fd5e67329cbbd75ebf</sha1>
  </revision>
  <revision>
    <id>299</id>
    <parentid>268</parentid>
    <timestamp>2025-02-23T17:38:20Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2593" xml:space="preserve">NFS or Networked File System is a protocol used to share filesystems over a network. [[IRIX 6.5]] includes support for NFSv2 and NFSv3.

== Hosting NFS ==
'''NFSv2 and NFSv3 have known security problems and exploits. It's highly advised to use a proper firewall and configuration.'''

NFS can be hosted from IRIX, BSD, Solaris/illumos, Linux or even some versions of macOS and still retain compatibility to IRIX. This page documents related issues with NFSv3/2 and the various quirks to get it working on each host OS.

=== Recommended Hosts ===
The easiest hosts to get working with IRIX are, in no particular order:

* illumos/Solaris
* FreeBSD
* NetBSD
* IRIX 6.5.22 or higher
* Windows 10 Pro or Enterprise

=== Not Recommended ===
These hosts have a number of server and implementation issues with NFSv3, if there are tricks unheard of yet to getting them working please feel free to add tricks below:

* Linux: rpcbind in Linux is buggy, and the nfsd module usually gets interfered with by SELinux, systemd and other modern Linuxisms.
* macOS: The most recent versions do not appear to have proper NFSv3 support for hosting, though NFSv3 connections do appear to work.

== Guides ==

==== FreeBSD ====
FreeBSD supports NFSv3 for IRIX easily.

'''Enabling Services'''

The following lines must be added to the /etc/rc.conf file:&lt;pre&gt;
rpcbind_enable="YES"

nfs_server_enable="YES"

mountd_enable="YES"

mountd_flags="-r -p 735"
&lt;/pre&gt;Now start the services:

&lt;code&gt;# service rpcbind start; service nfsd start; service mountd reload&lt;/code&gt;

'''Exporting'''

On ZFS, do not use /etc/exports. Instead, use:

&lt;code&gt;zfs sharenfs="-network 10.0.0.0 -mask 255.255.255.0" tank/protected&lt;/code&gt;

This will share the tank/protected dataset on LAN addresses 10.0.0.0/24

Further examples will include PF firewall rules to ensure spoofed/hostile traffic cannot compromise NFS.

==== Linux (Ubuntu) ====
Thanks to Larbob/lbdm for this guide.

'''Preparation'''

Install the NFS subsystem:

&lt;code&gt;sudo apt install nfs-kernel-server&lt;/code&gt;

Make an NFS share directory:

&lt;code&gt;sudo mkdir -p /srv/nfs&lt;/code&gt;

Set up /etc/exports with something like this:

&lt;code&gt;/srv/nfs 192.168.0.0/24(rw,sync,no_subtree_check,no_root_squash)&lt;/code&gt;

Edit /etc/default/nfs-kernel-server's RPCMOUNTDOPTS section to add --no-nfs-version 4

'''Finishing Touches'''&lt;pre&gt;
sudo exportfs -ra

sudo systemctl restart nfs-config

sudo systemctl restart nfs-kernel-server
&lt;/pre&gt;This will provide a setup to allow anyone with uid 0 to write as root. Please be careful if deciding this.

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>1fbcce7f525fa3cb4bcc0de3f869bc8ab5f1efed</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>File:IRIS 1000 Terminal.jpg</title>
  <ns>6</ns>
  <id>130</id>
  <revision>
    <id>260</id>
    <timestamp>2025-02-20T22:00:19Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="33" xml:space="preserve">An IRIS 1000 Terminal and monitor</text>
    <sha1>b5dcaf522509cc1307b9da4cd1cb488a3d10a118</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>File:SGI IRIS 2400.webp</title>
  <ns>6</ns>
  <id>131</id>
  <revision>
    <id>261</id>
    <timestamp>2025-02-20T22:10:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="35" xml:space="preserve">An IRIS 2400 owned by System Source</text>
    <sha1>4282fcdbb56f3f51c583cfa0ca20f2dff40cad1e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>68k-based SGIs (IRIS Series)</title>
  <ns>0</ns>
  <id>98</id>
  <revision>
    <id>262</id>
    <parentid>175</parentid>
    <timestamp>2025-02-20T22:10:16Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1868" xml:space="preserve">[[File:SGI IRIS 2400.webp|thumb|An IRIS 2000 owned by System Source]]
The earliest SGI systems were 68000-68020 powered graphics terminals and workstations running [[GL2]], a System V UNIX with an unusual for the time focus on graphics. Multibus standard powered machines, they were similar to Sun Multibus systems in many respects.

They were replaced by the [[Professional IRIS]] series of systems.

=== IRIS 1000 and 1200 ===
[[File:IRIS 1000 Terminal.jpg|left|thumb|An IRIS 2000 Terminal]]
The 1000 and 1200 computers used a Motorola 68000 microprocessor clocked at 8 Mhz and were sold as diskless systems intended for use as a terminal to a VAX system. The mainboard in the IRIS 1x00 machines is of Sun origin, existing before the founding of Sun Microsystems.

=== IRIS 1400 and 1500 ===
The 1400 and 1500 were equipped with a 10 MHz Motorola 68010 microprocessor, 1.5 MB of RAM and supported ST-506 or SMD drives. IRIS 1400 and 1500 used [[GL2-1.x|GL2 operating system]], Version 1. It uses a Geometry Engine VLSI GPU and 8-bit graphics planes of 1024x1024 memory. Additional memory, a floating point unit and a faster CPU were available. 

=== IRIS 2000 Series ===
The IRIS 2000 series includes the 2000 and 2200 terminals and the 2300, 2400 and 2500 workstations. These use the PM2 multibus board with a Motorola 68010 clocked at 10MHz. The SKYFPM-M-03 is an optional FPU board for these systems.  These systems supported a max of 2MB of RAM. 

=== IRIS 2000 Turbo ===
The 2300, 2400 and 2500 were later updated with a Turbo board, which used the IP2 68020 CPU at 14MHz and the FP1 floating point accelerator. They supported a max of 16MB RAM. 

=== IRIS Graphics ===
The IRIS Graphics system uses VLSI Geometry Engines and lacks any support for texturing. Within each GE is:

* 4 Matrix Engines
* 4-6 Clipper Engines
* 2 Scaler Engines

[[Category:Hardware]]</text>
    <sha1>ffe390ef8183b4dd82ca7f5df8b2c6c20d5a6feb</sha1>
  </revision>
  <revision>
    <id>298</id>
    <parentid>262</parentid>
    <timestamp>2025-02-23T17:37:34Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1860" xml:space="preserve">[[File:SGI IRIS 2400.webp|thumb|An IRIS 2000 owned by System Source]]
The earliest SGI systems were 68000-68020 powered graphics terminals and workstations running [[GL2]], a System V UNIX with an unusual for the time focus on graphics. Multibus standard powered machines, they were similar to Sun Multibus systems in many respects.

They were replaced by the [[Professional IRIS]] series of systems.

== IRIS 1000 Series ==
[[File:IRIS 1000 Terminal.jpg|left|thumb|An IRIS 2000 Terminal]]
The 1000 and 1200 computers used a Motorola 68000 microprocessor clocked at 8 Mhz and were sold as diskless systems intended for use as a terminal to a VAX system. The mainboard in the IRIS 1x00 machines is of Sun origin, existing before the founding of Sun Microsystems.

=== IRIS 1400 and 1500 ===
The 1400 and 1500 were equipped with a 10 MHz Motorola 68010 microprocessor, 1.5 MB of RAM and supported ST-506 or SMD drives. IRIS 1400 and 1500 used [[GL2-1.x|GL2 operating system]], Version 1. It uses a Geometry Engine VLSI GPU and 8-bit graphics planes of 1024x1024 memory. Additional memory, a floating point unit and a faster CPU were available. 

== IRIS 2000 Series ==
The IRIS 2000 series includes the 2000 and 2200 terminals and the 2300, 2400 and 2500 workstations. These use the PM2 multibus board with a Motorola 68010 clocked at 10MHz. The SKYFPM-M-03 is an optional FPU board for these systems.  These systems supported a max of 2MB of RAM. 

=== IRIS 2000 Turbo ===
The 2300, 2400 and 2500 were later updated with a Turbo board, which used the IP2 68020 CPU at 14MHz and the FP1 floating point accelerator. They supported a max of 16MB RAM. 

== IRIS Graphics ==
The IRIS Graphics system uses VLSI Geometry Engines and lacks any support for texturing. Within each GE is:

* 4 Matrix Engines
* 4-6 Clipper Engines
* 2 Scaler Engines

[[Category:Hardware]]</text>
    <sha1>89423e51bbdaf8965913fe73388e8afe9b2b8846</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Viewkit</title>
  <ns>0</ns>
  <id>132</id>
  <revision>
    <id>263</id>
    <timestamp>2025-02-20T22:12:14Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Viewkit is a C++ frontend toolkit for Motif allowing use of [[Motif]] in C++ contexts."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="86" xml:space="preserve">Viewkit is a C++ frontend toolkit for Motif allowing use of [[Motif]] in C++ contexts.</text>
    <sha1>f3978c106ac77133d4496bbbfa53c85f96db77d6</sha1>
  </revision>
  <revision>
    <id>264</id>
    <parentid>263</parentid>
    <timestamp>2025-02-20T22:20:17Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="464" xml:space="preserve">Viewkit is a C++ frontend toolkit for Motif allowing use of [[Motif]] in C++ contexts. It supports C++98 programing and is used in several SGI components, including the majority of desktop applications such as [[4dwm]],   [[Icon Catalog]], and the audio panel. 

=== Availability ===
Viewkit is a commercial product and available with the BX Pro package. A free, open source version called ViewKlass is available as well.

[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>77a12eb5cbb365bd727da8dd15d1bf0603e8a578</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Origin 3000</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>265</id>
    <parentid>185</parentid>
    <timestamp>2025-02-20T22:33:21Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6483" xml:space="preserve">[[File:Origin 3000 Rack Cluster.jpg|thumb|An Origin 3000 Rack cluster]]
The SGI Origin 3000, is the successor of the SGI [[Origin 2000]] line. Unlike previous versions, it did not offer a deskside version, opting for full and half rack configurations instead. It also introduced the "brick" architecture used by many Chimera architecture SGIs.

=== Features ===
Physically, the Origin 3000 is based on "bricks" - rackmounted modules that provide a specific function, that are connected together using NUMAlink 3 cables for modules providing compute functions, or Crosstown2 cables for modules providing I/O functions. These bricks are mounted in a standard 19-inch rack. There are two racks for the Origin 3000, a 17U-high half rack, and a 39U-high tall rack. Architecturally, the Origin 3000 is based on the distributed shared memory NUMAflex architecture. The NUMAlink 3 system interconnect uses a fat tree hypercube network topology.

The following table shows a list of models and their possible configurations:
{| class="wikitable"
|Model
|CPUs
|Memory
|Chassis
|-
|Origin 3200
|2 to 8
|Up to 16 GB
|Half Rack
|-
|Origin 3400
|4 to 32
|Up to 16 GB
|1 Full Rack
|-
|Origin 3800
|16 to 512
|Up to 1 TB
|1-16 Full Racks
|-
|Origin 3900
|4 to 512
|Up to 1 TB
|1 to 4 Full Racks
|}

==== C-Brick ====
[[File:Comparison of the O2k to the O3k.jpg|left|thumb|Comparison of the Origin 2000 and Origin 3000, side-by-side]]
The C-Brick (Compute Brick) is a 3U-high enclosure that contains CPUs on a PCB. The node contains two or four processors, the local and directory memory, and the Bedrock ASIC. The two processors and their secondary caches is contained on a PIMM (Processor Integrated Memory Module) daughter card that plugs into two 240-pin connectors on the node board. Initially, the Origin 3000 used the 360 MHz R12000 and the 400 MHz R12000A processors with 4 or 8 MB of secondary cache. In May 2001, the 500 MHz R14000 was introduced with 8 MB of secondary cache and in February 2002, the 600 MHz R14000A was made available. Near the end of its lifetime, the C-Brick was updated with 800 MHz MIPS processors.

==== CX-Brick ====
[[File:Origin 3000 Full Rack.jpg|thumb|An Origin 3000 Rack]]
The CX-Brick is a 4U-high enclosure that is only used in Origin 3900 and Onyx 3900 systems. It differs from the C-Brick by containing four node boards and eight-port router ASIC. The CX-Brick can support up to 16 processors and 32 GB of memory. The CX-Brick initially used the IP53 motherboard that supported 500 MHz R14000 and 600 MHz R14000A processors with 8 MB secondary caches, later upgraded to use the R16000 and R16000A. It connects to the system using NUMAlink 3.

=== R-Brick ===
The R-Brick (Router Brick) is a 2U-high enclosure that features an eight-port router ASIC. Its purpose is to route NUMAlink packets throughout the system to connect the C-Bricks together. R-bricks for the Origin 3400 have a router ASIC with two ports disabled to prevent them from being upgraded into Origin 3800 systems.

=== I-Brick ===
The I-Brick is a 4U-high enclosure that provides boot I/O functions for the Origin 3000. It features five hot swappable PCI-X slots, with three clocked at 33 MHz and two at 66 MHz on two separate buses, two sled-mounted 3.5-inch Fibre Channel hard drives and a proprietary CD-ROM drive. The I-Brick also provides a 10/100BASE-T Ethernet port, an IEEE-1394 port, a serial port, two USB ports as well as a real time clock and NVRAM for storing configuration information through the IO9. It connects to the system using Crosstown2.

==== IX-Brick ====
The IX-Brick is a 4U-high enclosure that is only used in Origin 3900 and Onyx 3900 systems. It an updated version of the I-brick with 133 MHz PCI-X expansion slots. It connects to the system using Crosstown2 cables.

=== V-Brick ===
The V-brick is a 4U-high enclosure that supports two InfinitePerformance (Commercial name for VPro/Odyssey Graphics) graphics pipes. Each graphics pipe consists of a 128 MB SGI VPro V12 graphics card. The V-brick connects to the system using Crosstown2 cables. This was one of two options for graphics.

=== G-Brick ===
The G-brick is a 18U-high enclosure that supports the InfiniteReality graphics subsystem. Each G-brick can support two InfiniteReality3 or InfiniteReality4 graphics pipes, although only one pipe can have four raster manager boards while the other can have two. The G-brick connects to the system using Crosstown2 cables.

==== Other Bricks ====
[[File:G-Brick.jpg|thumb|An Origin 3000 G-brick]]
Some systems were offered with D, P, PX and X Bricks. D is for data, and contains Fibre Channel, P and PX are PCI-X peripheral bricks, and X is an XIO brick.

=== Memory ===
The C-Brick supports 512 MB to 8 GB of local memory through eight DIMM slots organised into eight banks by using proprietary 100 MHz ECC DDR SDRAM DIMMs with capacities of 256 MB, 512 MB and 1 GB. The data path between the DIMM and the Bedrock ASIC is 144 bits wide, with 128 bits for data and 16 bits for ECC. Because the Origin 3000 uses a distributed shared memory model, directory memory is used to maintain cache coherency between the processors. Unlike the Origin 2000, which requires dedicated proprietary DIMMs for the directory memory, the Origin 3000's directory memory is integrated in the same DIMMs that contain the local memory. Due to this, there are two kinds of DIMM used in the Origin 3000: standard DIMMs, which supports systems with up to 128 processors, and premium DIMMs, which supports systems with more than 128 processors. The 256 MB DIMM is a standard DIMM, the 1 GB DIMM is a premium DIMM and the 512 MB DIMM can be either.

=== Power Supply ===
The Origin 3000 uses a "Power Bay" that contains up to 6 hot swappable powersupplies and provides the Bricks of the system with power (48VDC). It is connected to a wall outlet using a Power Distribution Unit. For this reason, most configurations require 240V. The 3400 and 3800 configurations had alternative setups for power.

=== L2 and L3 Controllers ===
The L2 and L3 Controllers are control systems used to manage the status of each brick in the system and to issue commands, monitor the environment and more. The L2 controller is a small Linux-based silver box that runs Linux on an embedded PowerPC system. The L3 controller was a Linux-based console that could manage several L2 systems.

=== Operating System Support ===
IRIX Versions from 6.5.15 to 6.5.30 supports the Origin 3000.

[[Category:Hardware]]</text>
    <sha1>6361ff89f006aeb3dae00388f0325b5713216955</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Personal IRIS</title>
  <ns>0</ns>
  <id>18</id>
  <revision>
    <id>266</id>
    <parentid>176</parentid>
    <timestamp>2025-02-20T22:34:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4793" xml:space="preserve">The Personal Iris was introduced in 1988 as low end workstation to the IRIS 4D series based on MIPS RISC microprocessors. A model name consists of "4D/" and a code designating the CPU and graphics type. The models replaced the "Twin Tower" style [[Professional IRIS]] series on the low end market, with the [[Power Series]] taking the higher end market. All Personal IRIS systems use a 32-bit MIPS I core and share some parts commonality with the R3000 Indigo in the 30 and 35 models. The last model (4D/35) was introduced in 1991 and presumably sold through 1993 with the release of the Indy heralding the end of the IRIS line.
[[File:PersonalIris.jpg|thumb|A 4D/35 owned by CB_HK of IRIXNet]]

=== Models ===
The series came in four models differentiated by badging, and the contents of the system module inside the case. No major external differences are otherwise shown. Between the 4D/2x and the 4D/3x systems are major differences. The latter one uses a totally different system board which besides faster processors includes a newly designed memory interface that allows much higher bandwidth and a larger amount of main memory. The system bus of the newer boards is clocked at 30 MHz instead of 10 MHz.
{| class="wikitable"
|Model
|CPU board
|CPU
|Maximum Memory
|-
|4D/20
|IP6
|MIPS R2000 12.5 MHz
|32MB
|-
|4D/25
|IP10
|MIPS R3000 20 MHz
|32MB
|-
|4D/30
|IP14
|MIPS R3000 30 MHz
|128MB
|-
|4D/35
|IP12
|MIPS R3000 36 MHz
|128MB
|}
The 20 and 25 models use industry standard 30-pin SIMMs. The 30 and 35 models use the same RAM modules as the Indigo R3000.

=== Graphics ===
The Personal IRIS had either a Datastation (Server) configuration, or they could utilize VME-based Eclipse or Express graphics, the latter only being usable on the 30 and 35 models due to a common architecture with the [[IRIS Indigo]]

=== Peripherals ===
The Personal IRIS, unlike later SGIs, does NOT possess support for PS/2 and uses the 4D-style DB9 keyboards used by the Personal/Professional IRIS series. To use PS/2 peripherals necessitates an adapter.

Personal IRIS models 4D/20 and 4D/25 have basic audio capabilities onboard. For audio in 4D/30 and 4D/35 an optional board is required that is plugged into a special slot on the mainboard. That additional board is called Magnum Audio Option and offers 16bit/stereo audio instead of the 8bit/mono audio that was offered on the earlier Personal Iris models.

The Personal IRIS has a built in SCSI controller that supports the internal as well as the external SCSI devices. The SCSI connector is located on the back of machine itself (just right of the E-Module) and is also covered by the plastic skin. The internal drives connect to the same SCSI chain that is also available via that external centronics SCSI port. The SCSI controller is narrow SCSI, Western Digital 33C93A.

All Personal IRIS systems allow the owner to install double height 6U VME devices. The VME interface of the Personal Iris also supports busmaster devices which may directly access the main memory of the computer. Only the 4D/30 and 4D/35 models allow VME block transfer due to a new peripheral controller on the system board.

=== Operating System Support ===
The Personal IRIS line was available during the "IRIX 3.x" era, but more contemporaneously called 4D1-3.x UNIX era. Support continued into IRIX 4.x and 5.x, and was removed along with all other 32-bit options by 5.3.

=== Hardware Problems ===

==== Power Supply ====
Power supply problems are not uncommon with these systems. Unplug the power cord, then open the opposite side of the E-Module and remove the sheetmetal. The power supply has 2 replaceable fuses which are worth to check as well as the proper cabling. One fuse is on the small daughtercard, the other is next to that card and usually covered with a blue plastic cap.

==== Onboard Battery ====
Signs of failure: The system fails to boot and returns to PROM after issuing "Can't set tod clock"

This problem has so far been seen only on the later Personal Iris models (4D/30 and 4D/35). The earlier systems may not be affected and just boot with a faulty date/time.

While there also may be other causes, the by far most likely is an empty battery on the CPU board. The original battery is a 3V coin cell made by Duracell (DL2450). The battery is socketed so replacing it doesn't require any soldering. The cost of the battery is approximately 3 USD / 2 EUR.

==== 4MB Memory Modules ====
Signs of failure: System doesn't work when more than one set of 4MB modules is installed.

This is a known problem and a flaw in the systems hardware of 4D/30 and 4D/35 systems which can not be fixed. The bottom line is, that only one 16MB kit (4x4MB) may be installed - there is no limitation regarding 8MB (4x2MB) or 32MB (4x8MB) kits.
[[Category:Hardware]]</text>
    <sha1>3164d88d20be932f9cc07c613a3a76c72b237a7f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>RISC/OS</title>
  <ns>0</ns>
  <id>97</id>
  <revision>
    <id>267</id>
    <parentid>207</parentid>
    <timestamp>2025-02-20T22:40:52Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="512" xml:space="preserve">'''RISC/OS''', also known as '''UMIPS''' was an early UNIX produced by MIPS Computer Systems, and a predecessor of both 4D1 and IRIX. Unlike [[GL2-3.x|GL2]], RISC/OS had roots in both BSD and System V. When SGI purchased MIPS, it was succeeded by [[4D1-1.x]].

=== Versions ===
It was referred to as '''UMIPS''' between releases 1 through 3. 4.x and onwards were RISC/OS. The final release, based on Release 4 of System V, was released in 1991. 
[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>d08a7b7b948e5811f2db40729c814785c77c470b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>File:SGI Fuel.jpg</title>
  <ns>6</ns>
  <id>133</id>
  <revision>
    <id>269</id>
    <timestamp>2025-02-20T22:51:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="31" xml:space="preserve">SGI Fuel, viewed from the front</text>
    <sha1>a01e7ab095181bb35155c6ecda5f6eadb199b122</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Fuel</title>
  <ns>0</ns>
  <id>115</id>
  <revision>
    <id>270</id>
    <parentid>217</parentid>
    <timestamp>2025-02-20T22:52:07Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5976" xml:space="preserve">The Silicon Graphics Fuel, introduced in 2002, was intended to be a single-CPU midrange solution for those customers who did not need multiple-CPU capability, thus offering a much cheaper system compared to a baseline Tezro or top-spec single-CPU [[Octane]]. Contrary to popular belief, Fuel was not a successor to [[O2]]. SGI never made a follow-on to O2; a new system was designed (internally known as the Banana2000 or b2k) but was never developed beyond a prototype.The Fuel has a somewhat contentious reputation in the enthusiast community. In terms of form-factor and internal design, it is the most "PC-like" of the MIPS workstations, sharing much of its design with the Visual Workstation 230. Due to SGI's need to cut costs the Fuel is also likely the most error-prone workstation that SGI produced, with frequent failures of power supplies, mainboards, and environmental monitoring which most heavily plagued early revisions. The frequent failures also means a shortage of available parts, and what parts are available are expensive. So while the Fuel was meant to be a reduced-cost version of the Origin 300 architecture, it is actually the most expensive MIPS desktop to own.

=== Features ===
[[File:SGI Fuel.jpg|left|thumb|An SGI Fuel]]
Fuel shares the IP35-architecture with Origin 300, Origin 350, Origin 3000, Onyx 3000 and Tezro systems.In terms of design, it is closest to a single-node Origin 300 with graphics, based on the environmental monitoring and other support chips.

The design is very similar to a standard ATX PC with the exception of the memory/CPU positions and the XIO2, used for graphics, being below the PCI-X expansion slots, meaning the board is longer and wider than a typical ATX motherboard.

==== CPU ====
The Fuel is a single processor system and can take either:

* One R14000 CPU at either 500 or 600MHz
* One R16000 CPU at 700, 800 or (rarely) 900Mhz

==== Memory ====
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Origin 300, Origin 350, and the Tezro. There are a total of four slots, organized into two banks of two slots. This results in a memory capacity from 512 MBytes to 4 Gbytes total system memory.

All DIMMS for the Fuel use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory, which remains unused in the Fuel. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

==== Graphics ====
The Fuel can have one XIO 2 graphics card, either the V10 configuration with 32MB of texture memory or the V12 with 128MB of texture memory. A dual-channel display card can be attached to offer dual head display.

==== I/O ====
Internally, the boot drive attaches to the mainboard with a 68-pin SCSI cable. Unfortunately, the connector on the mainboard itself is *not* a standard 68-pin connector and is actually a proprietary socket used only by the Fuel. Rough handling of the swivel-out hard drive tray is known to fray these cords, making them a difficult part to source.

The Fuel is the only MIPS workstation to have a USB-controller built-in. As such, USB sound cards are common alternatives to PCI for Fuel users.

Four PCI-X slots are provided, two at 66MHz and two at 33MHz.

==== Power Supply ====
The Fuel used several different power supplies over the life of the model. These units conform loosely to the WTX specification, a standard similar to ATX but more oriented towards servers. Unfortunately the Fuel is different enough that neither WTX nor ATX power supplies will not work without modification. It is believed that SGI also requested other changes for this application, including a special monitoring circuit.

=== Operating System Support ===
IRIX Versions from 6.5.17 through 6.5.30 are supported on this machine. Firewire support became functional around 6.5.27

==== Hardware Problems ====
The Fuel's cheap design has lead to many common points of failure that can destroy a system:

==== Motherboard Failures ====
Capacitor failure is common on these boards and some just mysteriously die without a cause.

==== Inadequate Ventilation ====
The CPU boards is located at the front of the case, and the memory is in front of it for airflow. This results in insufficient airflow to the CPU which can result in failures.

The same is true for the XIO2 graphics board. They are notoriously prone to failure due to either fan failure or lack of ventilation. There are no easy workarounds that exist.

==== Fans ====
The fans are tied to the environmental monitoring system and do not use the standard pinouts. This section will eventually link to a separate page discussing this.

==== Power Supply Failure ====
Fuel power supplies are variants of off-the-shelf units offered for consumer PCs. However the pinouts, if not the voltages and functions, differ even though the OEM part numbers do not. An ATX adapter is available from Kuba Tyszko but it should be noted that this should only be used with ATX power supplies that are capable of providing 30 amps on both the 3.3v and 5v rails, which is somewhat uncommon.

==== Environmental Monitoring ====
Temperature sensing on early Fuel mainboards is notoriously prone to failure, rendering the computer inoperable if environment monitoring is left on. Turning it off can allow a boot, but is not recommended.

[[Category:Hardware]]</text>
    <sha1>b7295a77f3d70961349f6b05a2ae576f4d6175e6</sha1>
  </revision>
  <revision>
    <id>301</id>
    <parentid>270</parentid>
    <timestamp>2025-02-23T17:39:13Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5972" xml:space="preserve">The Silicon Graphics Fuel, introduced in 2002, was intended to be a single-CPU midrange solution for those customers who did not need multiple-CPU capability, thus offering a much cheaper system compared to a baseline Tezro or top-spec single-CPU [[Octane]]. Contrary to popular belief, Fuel was not a successor to [[O2]]. SGI never made a follow-on to O2; a new system was designed (internally known as the Banana2000 or b2k) but was never developed beyond a prototype.The Fuel has a somewhat contentious reputation in the enthusiast community. In terms of form-factor and internal design, it is the most "PC-like" of the MIPS workstations, sharing much of its design with the Visual Workstation 230. Due to SGI's need to cut costs the Fuel is also likely the most error-prone workstation that SGI produced, with frequent failures of power supplies, mainboards, and environmental monitoring which most heavily plagued early revisions. The frequent failures also means a shortage of available parts, and what parts are available are expensive. So while the Fuel was meant to be a reduced-cost version of the Origin 300 architecture, it is actually the most expensive MIPS desktop to own.

== Features ==
[[File:SGI Fuel.jpg|left|thumb|An SGI Fuel]]
Fuel shares the IP35-architecture with Origin 300, Origin 350, Origin 3000, Onyx 3000 and Tezro systems.In terms of design, it is closest to a single-node Origin 300 with graphics, based on the environmental monitoring and other support chips.

The design is very similar to a standard ATX PC with the exception of the memory/CPU positions and the XIO2, used for graphics, being below the PCI-X expansion slots, meaning the board is longer and wider than a typical ATX motherboard.

==== CPU ====
The Fuel is a single processor system and can take either:

* One R14000 CPU at either 500 or 600MHz
* One R16000 CPU at 700, 800 or (rarely) 900Mhz

==== Memory ====
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Origin 300, Origin 350, and the Tezro. There are a total of four slots, organized into two banks of two slots. This results in a memory capacity from 512 MBytes to 4 Gbytes total system memory.

All DIMMS for the Fuel use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory, which remains unused in the Fuel. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

==== Graphics ====
The Fuel can have one XIO 2 graphics card, either the V10 configuration with 32MB of texture memory or the V12 with 128MB of texture memory. A dual-channel display card can be attached to offer dual head display.

==== I/O ====
Internally, the boot drive attaches to the mainboard with a 68-pin SCSI cable. Unfortunately, the connector on the mainboard itself is *not* a standard 68-pin connector and is actually a proprietary socket used only by the Fuel. Rough handling of the swivel-out hard drive tray is known to fray these cords, making them a difficult part to source.

The Fuel is the only MIPS workstation to have a USB-controller built-in. As such, USB sound cards are common alternatives to PCI for Fuel users.

Four PCI-X slots are provided, two at 66MHz and two at 33MHz.

==== Power Supply ====
The Fuel used several different power supplies over the life of the model. These units conform loosely to the WTX specification, a standard similar to ATX but more oriented towards servers. Unfortunately the Fuel is different enough that neither WTX nor ATX power supplies will not work without modification. It is believed that SGI also requested other changes for this application, including a special monitoring circuit.

== Operating System Support ==
IRIX Versions from 6.5.17 through 6.5.30 are supported on this machine. Firewire support became functional around 6.5.27

==== Hardware Problems ====
The Fuel's cheap design has lead to many common points of failure that can destroy a system:

==== Motherboard Failures ====
Capacitor failure is common on these boards and some just mysteriously die without a cause.

==== Inadequate Ventilation ====
The CPU boards is located at the front of the case, and the memory is in front of it for airflow. This results in insufficient airflow to the CPU which can result in failures.

The same is true for the XIO2 graphics board. They are notoriously prone to failure due to either fan failure or lack of ventilation. There are no easy workarounds that exist.

==== Fans ====
The fans are tied to the environmental monitoring system and do not use the standard pinouts. This section will eventually link to a separate page discussing this.

==== Power Supply Failure ====
Fuel power supplies are variants of off-the-shelf units offered for consumer PCs. However the pinouts, if not the voltages and functions, differ even though the OEM part numbers do not. An ATX adapter is available from Kuba Tyszko but it should be noted that this should only be used with ATX power supplies that are capable of providing 30 amps on both the 3.3v and 5v rails, which is somewhat uncommon.

==== Environmental Monitoring ====
Temperature sensing on early Fuel mainboards is notoriously prone to failure, rendering the computer inoperable if environment monitoring is left on. Turning it off can allow a boot, but is not recommended.

[[Category:Hardware]]</text>
    <sha1>aad1756a97c9d33ac87c2df5c4dbd1a11850f7c2</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>MEX</title>
  <ns>0</ns>
  <id>126</id>
  <revision>
    <id>271</id>
    <parentid>243</parentid>
    <timestamp>2025-02-20T22:55:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="611" xml:space="preserve">MEX is a GL accelerated, stacking window system for [[GL2-2.x|GL2]], one of two predecessors of the 4D1 operating system. MEX is a simplistic graphics windowing system with everything launched from a terminal window, similar to other early window managers. As it did not use X11 or Postscript-based [[4Sight]] it was exceptionally quick, if impractical to build applications for.  

MEX was included with all versions of GL2 but was never used by 4D1 or later SGI systems and neither was backwards compatibility considered.  
[[File:MEX.png|thumb|MEX Demonstration on a 68k-based IRIS]]

[[Category:Subsystems]]</text>
    <sha1>266174a3a928b45947394089d74326e78cb51e79</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>How to Find Commercial Software</title>
  <ns>0</ns>
  <id>107</id>
  <revision>
    <id>272</id>
    <parentid>166</parentid>
    <timestamp>2025-02-20T22:56:29Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="756" xml:space="preserve">Software for IRIX can be acquired a number of ways:

=== Requesting Software ===
IRIXNet's policies allow users to request software in the [https://forums.irixnet.org/thread-2258.html Commercial Software Request Megathread] where users can share such things over private messaging.

=== Purchasing Software ===
IRIXNet and SGUG both have forums for selling software. Additionally, eBay and other places are sources for this. 

=== Dealing with the Licenses ===
Two forms of licensing for IRIX were common: [[Flexlm]] and dongles. Dealing with the former is just a matter of getting a valid license and placing it into the license.dat. Dealing with the latter necessitates using cracks to patch the executable.

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>0471a9a26f56a44bc2efe90c5915faa247acec1a</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>MIPSPro</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>273</id>
    <parentid>202</parentid>
    <timestamp>2025-02-21T20:27:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13340" xml:space="preserve">MIPSPro is the IRIX-native C/C++/FORTRAN compiler that was distributed by SGI for use in IRIX development.

This page serves to document MIPSPro's behavior, characteristics, compatibility, and differences from other UNIX-style cc compilers and the GNU Compiler Collection.

For legacy MIPSPro releases and documentation, see [[IRIS Development Option]] for more info.

=== General ===
MIPSPro is not installed in a standard IRIX install and requires a collection of other discs that contain the compiler, development libraries/header files, toolchain and supporting utilities.

MIPSPro supports three ABIs, O32, N32 and N64 (Not to be confused with the Nintendo 64). The O32 ABI is the MIPSII 32-bit ABI, and stands for Old 32. The N32 ABI is analogous to the Intel x32 ABI used on x64 systems to provide enhancements to 32-bit programs through using 32-bit pointers while offering many of the N64 ABI enhancements over O32. The N64 ABI is the native 64-bit ABI for IRIX.

Several compiler front ends were available, including the C, C++ and FORTRAN compilers. Others may have possibly been available at various points historically.

=== Optimization ===
MIPSPro supports -O0,1,2,3, and fast flags, as well as a number of other optimization/architecture flags:

-mips4 will enable the MIPS IV instruction set

-TARG will enable platform or CPU-specific optimizations

-OPT can tune various optimizations

For a full list, please check: &lt;nowiki&gt;https://irix7.com/techpubs/007-2360-006.pdf&lt;/nowiki&gt;

==== TARG flag ====
The TARG flag controls both platform and CPU specific optimizations and will take a variety of commands:

-TARG:proc=R10000 will, combined with the MIPSIV flag, compile for MIPS IV platforms and enable specific optimizations for the R10000 processors. The resulting binary will run on R5000 and R8000 systems, but will skip the optimizations for those platforms.

-TARG:platform=IP30 will, combined with other flags, enable Octane specific optimizations.

The two commands can be combined as so: -TARG:platform=IP30:proc=R10000 as well as other commands.

==== OPT flag ====
This has a number of useful flags for more carefully optimizing code.

-OPT:space Optimizes the program for size, similar to the GCC -Os flag

-OPT:Olimit=n This sets a cutoff limit on procedure sizes to optimize. Procedures above the set size will be left alone. The compiler will normally during compilation throw notices out advising of potential ways to tune this.

-OPT:alias=value The compilers must normally be very conservative in optimization of memory references involving pointers (especially in C), since aliases (that is, different ways of accessing the same memory) may be very hard to detect. This option may be used to specify that the program being compiled avoids aliasing in various ways. See the above document for various applications.

Other flags are listed in the above document

=== C Programming with MIPSPro ===
Much like GCC and other modern compilers, MIPSPro can be called from the commandline like so:

&lt;code&gt;% cc foo.c&lt;/code&gt;

Where foo.c is a presumably simple test file.

MIPSPro's ABI, compiling and configuration is via &lt;code&gt;/etc/compiler.defaults&lt;/code&gt;. This can be overridden with compile-time flags, or ENV variables. SGI_ABI, for instance, controls the active ABI:

&lt;code&gt;% setenv SGI_ABI -n32&lt;/code&gt;

This will set it to -n32 mode.

==== Strictness ====
MIPSPro is far more strict than GCC about accepting standard C code and its compiler infrastructure is entirely different. Common bad programming techniques that work in GCC may not work on MIPSPro, this section aims to document common pitfalls:

=====Variable Attributes=====

These are not supported, so they have to be patched with #ifdef or removed:

&lt;code&gt;__attribute__(( XXX ))&lt;/code&gt;

This is the structure of these.

One variable attribute can be rewritten to work with MIPSPro: the attribute 'packed' for a struct can be enforced in MIPSPro by placing the struct between two pragma blocks:

&lt;pre&gt;#if defined (__sgi)

+#pragma pack(1)

+#endif

struct {

...

};

&lt;nowiki&gt;#&lt;/nowiki&gt;if defined (__sgi)

+#pragma pack(0)
+#endif
&lt;/pre&gt;

=====Zero Length Arrays=====

This is a GNU extension prior to c99. Using c99 or -c99 flag for cc should allow it to work.

=====Variable Length Arrays=====

Only supported using the c99 driver or -c99.

=====String Literals=====

IRIXNet staff Dexter1 helpfully pointed this out in a forum post:

Shorthand initialization of char a[] = " "; with MIPSpro will go wrong with leading zero bytes. Rewrite that code.

What follows is his example copied mostly-verbatim:
&lt;pre&gt;
&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;stdio.h&gt;

&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;stdlib.h&gt;

&lt;nowiki&gt;#&lt;/nowiki&gt;include &lt;memory.h&gt;

int main(void) {

const char a[] = "\0This is a text";

const char b[] = { 0x0, 'T', 'h', 'i', 's', ' ', 'i', 's', ' ', 'a',

' ', 't', 'e', 'x', 't', 0x0 };

const char *c = "\0This is a text";

char buf1[128];

char buf2[128];

char buf3[128];

size_t lena = sizeof(a) - 1;

size_t lenb = sizeof(b) - 1;

size_t lenc = 15;

memcpy(buf1,a,lena);

memcpy(buf2,b,lenb);

memcpy(buf3,c,lenc);

printf("length a : %d, length b %d, length c %d\n", lena, lenb, lenc);

printf("buf11 : %x, buf21 : %x, buf31 : %x\n", buf11, buf21, buf31);

printf("comparing a with buf1 : %d \n", memcmp(a,buf1,lena));

printf("comparing b with buf2 : %d \n", memcmp(b,buf2,lenb));

printf("comparing c with buf3 : %d \n", memcmp(c,buf3,lenc));

printf("comparing buf1 with buf2 : %d \n", memcmp(buf1,buf2,lena));

printf("comparing buf1 with buf3 : %d \n", memcmp(buf1,buf3,lenc));

printf("comparing buf2 with buf3 : %d \n", memcmp(buf2,buf3,lenb));

return 0;
}
&lt;/pre&gt;
Consider this code. The three text containers a, b and c are initialized differently but all should contain "This is a text" preceded and suffixed by a zero byte.

* Container a's type is an array of char. Its lifetime is limited to the main scope and its initialized content gets put on the stack by the compiler.
* Container b is the longer version of a and is also typed array of char.
* Container c is a pointer to a read-only memory block of chars allocated and initialized by the compiler on the heap.

If compiled with MIPSpro cc or c99 and ran, it becomes apparent that array a is not initialized properly. a1 should contain capital 'T' but instead it's a zero byte: once looking at the stack where a is put with a debugger, there is nothing: The preceding zero byte interferes with compiler code and the stack, although it will allocate the correct amount of bytes on the stack, will only contain zeroes.

This 'shorthand' initialization of an array is often used in modern opensource software, and is particularly prevalent in test suites, where binary headers and unicode data content are initialized in arrays to test functions.

String Concatenation

GCC will accept the following code, by concatenating the strings:

&lt;code&gt;puts( "abc" "def" );&lt;/code&gt;

This is going to not work on MIPSPro's c89, but will on c99. A tutorial on how to fix it is below:

&lt;code&gt;puts( "abcdef" );&lt;/code&gt;

This can work here, alternatively this would too:
&lt;pre&gt;
char buff[ 255 ];

bzero( buff, 0, 255);

strcat( buff, "abc" );

strcat( buff, "def" );
&lt;/pre&gt;

=====Arithmetic On Pointers=====

The gcc compiler allows pointer arithmetic on void pointers. For example, gcc allows

void *foo;

foo += 5;

When using MIPSpro, the pointer must be cast to a type with a size:

void *foo;

foo = (char*)foo + 5;

lvalues

gcc allows the use of casts as lvalues. For example:

void *foo;

(char*)foo += 5;

When using MIPSpro, casts cannot be lvalues:

void *foo;

foo = (char*)foo + 5;

=====Block Expressions=====

gcc allows block expressions, such as ({x++});. When using MIPSPro compilers, remove the extra parentheses.

=====Portable Types=====

Occasionally code that works on other platforms will compile fine on IRIX, but will misbehave when run. These problems can be difficult to track down, but one thing to check for is assumptions about whether char is signed or unsigned. IRIX compilers default to unsigned. It's recommended to check for this.

Setting up parallel debugging sessions and stepping through the working and non-working code simultaneously to find where they diverge is often helpful.

Alternatively, try to recompile the code with the MIPSPro option -signed in CFLAGS. This will treat variables with type char as if they are signed char.

setenv() missing in IRIX

Raion's libxg library has solved this, see it for an example.

=====POSIX Threads and Reentrancy=====

The pthread implementation under Irix is mostly the standard pthreads - there is however a caveat in the form of #defines that are necessary.

&lt;code&gt;CPPFLAGS="-D_SGI_MP_SOURCE -D_SGI_REENTRANT_FUNCTIONS"&lt;/code&gt;

SGI recommended these back when their technical documentation library was a thing - and certainly the first define alters the behavior of the general error indicator errno. Without _SGI_MP_SOURCE individual threads receive separate and unique errno addresses.

If there is unusual behavior regarding threads not sharing or unexpectedly sharing data, one may be missing one of the above.

=====Line terminators=====

The ANSI specification leaves the determination of valid line terminators to the compiler implementors. MIPSpro allows ^J, while GCC allows both ^J and ^M. The &lt;code&gt;to_unix&lt;/code&gt; command will convert files containing DOS-style ^M line terminators to the UNIX standard ^J form.

=====Pseudo Function Macros=====

gcc allows the non-standard &lt;code&gt;__FUNCTION__&lt;/code&gt; and &lt;code&gt;__PRETTY_FUNCTION__&lt;/code&gt; pseudo-macros. These are not true macros, so one must use &lt;code&gt;_GNUC__&lt;/code&gt; to test for them. As of IRIX 6.5.18, the c99 func macro is available, which expands to a function name.

=====Extern Inline Functions=====

The gcc compiler treats extern inline functions as being extern,while the MIPSpro compilers treat them as inline. To get equivalent behavior, remove the inline keyword.

=====Inline defines in C code=====

Pre-c99 C code often define an INLINE macro being set to &lt;code&gt;inline&lt;/code&gt; MIPSPro cc compiler instead uses &lt;code&gt;__inline&lt;/code&gt; MIPSPro's c99 compiler follows the c99 standard and will inline function with the &lt;code&gt;inline&lt;/code&gt; keyword.

getopt_long() missing in IRIX

Raion had added a compat/getopt.h to libxg

=====Compiler Identification=====

To pass specific code using an identification macro, the &lt;code&gt;__sgi&lt;/code&gt; macro can be used to reliably define MIPSPro-related code (or IRIX specific code in general, this can be combined with gnu macros to make paths for both gcc and MIPSPro)

=====Warning Sanitizing=====

MIPSPro is very pedantic with warnings. This can be used in Makefiles to make it less pedantic and behave more like GCC:
&lt;pre&gt;
NOWARN = -woff 1009,1014,1110,1116,1185,1188,1204,1230,1233 \

-Wl,-woff,85,-woff,84
$(CC) $(NOWARN) ...&lt;/pre&gt;

It is highly encouraged to do a normal pass and capture the warnings it gathers anyways, as these can provide some insight into potential mismatches and other issues.

=== C99 Specifics ===
MIPSPro provides C99 compatibility via the c99 driver.

The C99 implementation in MIPSPro is quite good, but unlike standard cc, which is not C99 compliant, it offers far more features:

=== C++-Style Comments ===
By default, the cc driver does not allow // comments to be used. To use //, either use the c99 driver, or set flag -Xcpluscomm in the CFLAGS.

=== Function Macros ===
As previously stated, all versions of IRIX since 6.5.18 support the function pseudomacro.

=== Variadic Macros ===
Unsupported in MIPSPro. A rumor of them being supported seems to have been unfounded. Variadic function (e.g. functions with optional arguments) are supported, however. 

=== Format problems in printf for variables with size_t and ssize_t ===
In MIPSPro one cannot use the format strings %zu for size_t types and %zd for ssize_t types. Use %lu and cast both types to unsigned long to print out these variables. Failure to do so will result in unexpected crashes when the program reaches those printf statements.

More to be added as they are discovered.

== Compiler Drivers ==
The driver commands cc, c99, CC, f90, and f77 call subsystems that compile, optimize, assemble, and link source. This section describes the default behavior for compiler drivers.

At compilation time, it is possible to select one or more options that affect a variety of program development functions, including debugging, profiling, and optimizing. It's also possible to specify the names assigned to output files. Note that some options have default values that apply if not specified.

When one invokes a compiler driver with source files as arguments, the driver calls other commands that compile the source code into object code. It then optimizes the object code (if requested to do so) and links together the object files, the default libraries, and any other libraries specified.

Given a source file foo.c, the default name for the object file is foo.o. The default name for an executable file is a.out. The following example compiles source files foo.c and bar.c with the default options:

&lt;code&gt;% cc foo.c bar.c&lt;/code&gt;

This example produces two object files, foo.o and bar.o, and links them with the default C library, libc , to produce an executable called a.out.

[[Category:Compilers]]</text>
    <sha1>91d7dded22bce7d7d4466c31b36d7ff2f8117fab</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>User talk:Raion</title>
  <ns>3</ns>
  <id>127</id>
  <revision>
    <id>274</id>
    <parentid>246</parentid>
    <timestamp>2025-02-21T22:15:08Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1885" xml:space="preserve">Nekoware Draft.

Nekoware is a community project targeting IRIX 6.5.21 or later (most commonly .22 and .30) MIPS IV systems. 

It is a high performance, well-optimized group of LTS supported software. Each package has a maintainer. 

Nekoware is released on a quarterly basis, with the newest iteration of it starting at 2025-Q2. 

Each quarter, the entire base release is rebuilt. Not all packages are turned over, but many are. 

Building:

This is the official N32 Nekoware build environment standard:

setenv CC c99
setenv CXX CC
setenv CFLAGS '-O2 -mips4 -TARG:proc=r10000'
setenv CXXFLAGS '-O2 -mips4 -TARG:proc=r10000'
setenv CPPFLAGS '-I/usr/nekoware/include -I/usr/include'
setenv LDFLAGS '-L/usr/nekoware/lib32 -L/usr/lib32 -Wl,-rpath -Wl,/usr/nekoware/lib32'
setenv PKG_CONFIG '/usr/nekoware/bin/pkgconfig'
setenv PKG_CONFIG_PATH '/usr/nekoware/lib32/pkgconfig'
setenv ACLOCAL 'aclocal -I/usr/nekoware/share/aclocal/'


Additional opts can be added as necessary as well as ENV vars. 

GCC Policy:

Nekoware does primarily build software with MIPSPro, but in light of GCC advancements and the fact it's a decent compiler, it is permitted for software. The following caveats for making GCC packages apply:

GCC does not play nice with the C++ of MIPSPro. The C++ ABIs are dissimilar so any projects making use of C++ must reduplicate their C++ dependencies at minimum. 

Paths for GCC libs and includes are:

/usr/nekoware/gcc-include
/usr/nekoware/gcc-lib32

GNOME, KDE and FreeDesktop projects Policies:
We wish to avoid integrating security and bloat issues into IRIX where possible. As such, we do not permit most GNOME and KDE dependencies, and even less FreeDesktop libs. This can include:

Policykit
Consolekit
dbus/messagebus
GNOME bonobo/KDE DCOP/CORBA

Such systems are better suited for the likes of SGUG-RSE. 

Otherwise, go wild. We accept any packages otherwise.</text>
    <sha1>38b3bd48795cce6cf59504940f9b234bde747219</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Reddit</title>
  <ns>0</ns>
  <id>104</id>
  <revision>
    <id>275</id>
    <parentid>163</parentid>
    <timestamp>2025-02-22T16:31:14Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="344" xml:space="preserve">Reddit has several SGI subreddits. 

=== List of Subreddits ===
[https://reddit.com/r/sgi /r/sgi] run by [[IRIXNet]] staff

[https://irixnet.org/r/irix /r/irix]jointly run by [[IRIXNet]] and [[SGUG]]

[https://reddit.com/r/silicongraphics /r/silicongraphics] independently run

[[Category:Communities]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>bf6880d7181beeb23574cae0e2631c98510bcf6b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Installing IRIX</title>
  <ns>0</ns>
  <id>13</id>
  <revision>
    <id>276</id>
    <parentid>169</parentid>
    <timestamp>2025-02-22T16:33:48Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="916" xml:space="preserve">It is recommended to install IRIX via a network for ease of use. IRIX has a rather unique and comprehensive network installing method, and as a result of it's convenience, performance and utility, many users have created guides on how to do it. This serves as the meta hub. 

=== General ===
The following network protocols must be used to network install IRIX:

* rsh
* tftp
* bootp

The host must in most cases be a UNIX compatible with UNIX permissions, on the same LAN. IRIX PROMs do not possess routing, ICMP echoes (It cannot respond to pings), or the ability to take HTTP or rsync.

=== Guides ===
This subsection offers specific guides for installation with various host operating systems.

==== IRIX ====

* [[IRIX Install using IRIX Host]]

==== NetBSD ====

* [[IRIX Install using NetBSD Host]]

===== Reanimator =====

* [[Using Reanimator to Install IRIX]]

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>a2fc705a859cf1e28f6b3eb905e66c1823b5498d</sha1>
  </revision>
  <revision>
    <id>296</id>
    <parentid>276</parentid>
    <timestamp>2025-02-23T06:34:39Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* General */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1008" xml:space="preserve">It is recommended to install IRIX via a network for ease of use. IRIX has a rather unique and comprehensive network installing method, and as a result of it's convenience, performance and utility, many users have created guides on how to do it. This serves as the meta hub. 

=== General ===
The following network protocols must be used to network install IRIX:

* rsh
* tftp
* bootp

The host must in most cases be a UNIX compatible with UNIX permissions, on the same LAN. IRIX PROMs do not possess routing, ICMP echoes (It cannot respond to pings), or the ability to take HTTP or rsync.

=== Guides ===
This subsection offers specific guides for installation with various host operating systems.

==== IRIX ====

* [[IRIX Install using IRIX Host]]

==== NetBSD ====

* [[IRIX Install using NetBSD Host]]

===== Reanimator =====

* [[Using Reanimator to Install IRIX]]

=== Using CDs ===

* [[CD Installation of IRIX|CD Installation of IRIX (Not Recommended)]]

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>f834d1ef6f0ec982e6b86c49b06060568fda62ad</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Using Reanimator to Install IRIX</title>
  <ns>0</ns>
  <id>134</id>
  <revision>
    <id>277</id>
    <timestamp>2025-02-22T16:44:59Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Reanimator is a specially created Linux VM for Virtualbox and Raspberry Pi systems. It can install IRIX on most systems.   This guide is derived from their official documentation  === Setting IP client address in Command Monitor === To enter Comand Monitor, boot the target machine and click on "Stop for Maintenance dialog" or press Esc. Click on "Enter Command Monitor" or press "5" (on Indy, numbers can change on other sgi model).  Two IP client addresses are available:..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9420" xml:space="preserve">Reanimator is a specially created Linux VM for Virtualbox and Raspberry Pi systems. It can install IRIX on most systems. 

This guide is derived from their official documentation

=== Setting IP client address in Command Monitor ===
To enter Comand Monitor, boot the target machine and click on "Stop for Maintenance dialog" or press Esc. Click on "Enter Command Monitor" or press "5" (on Indy, numbers can change on other sgi model).

Two IP client addresses are available:

IRIS: setenv netaddr 192.168.9.1

or

IRIS2: setenv netaddr 192.168.9.2

To reboot from disk 1 after the installation, run in Command Monitor:
 &lt;code&gt;&gt;&gt;setenv SystemPartition dksc(0,1,8)
 &gt;&gt;setenv OSLoadPartition dksc(0,1,0)
 &gt;&gt;setenv OSLoader sash
 &gt;&gt;setenv OSLoadFilename unix&lt;/code&gt;

=== Starting the partition tool in Command Monitor ===
Examples on how to start fx, the partitioning tool:
IRIX systems using a 32-bit kernel (e.g. any pre-ARCS SGIs, the Indy, O2, Indigo2 R4000 etc.) use fx.ARCS, all others use fx.64


32-bits:

bootp():IRIX/6.5.22/ovl1/stand/fx.ARCS -x

bootp():IRIX/irix53/1/stand/fx.ARCS -x

bootp():IRIX/irix62/1/stand/fx.ARCS -x

bootp():IRIX/irix650/1/stand/fx.ARCS -x

bootp():IRIX/irix657/1/stand/fx.ARCS -x

64-bits:

bootp():IRIX/6.5.30/disc1/stand/fx.64 -x

bootp():IRIX/irix650/1/stand/fx.64 -x

bootp():IRIX/irix657/1/stand/fx.64 -x

=== Creating a disklabel ===
A disklabel cannot format the contents of a drive. Unlike MS Windows, a format command in UNIX is mkfs. This will be 

covered later. 

Press Enter a couple of times to select the default system disk on SCSI controller 0, ID 1, lun 0

fx&gt; [l]abel

fx/label&gt; [c]reate

fx/label/create&gt; [a]ll

fx/label/create&gt; ..

fx/label&gt; [sy]nc

fx/label&gt; ..

fx&gt; [r]epartition

fx/repartition&gt; [ro]otdrive

fx/repartition/rootdrive: type of data partition = (xfs)

fx/repartition&gt; /exit

=== Starting the installer from network ===
- Enter System Maintenance menu, press 2 or click on "Install system software"

- Press 2 or click on "From remote directory"

- Enter "rbpi" or "debian" (according to the installation platform) as "server name", NOT the IP address

- For example:

Indy:

IRIX/6.5.22/ovl1/dist

Octane2:

IRIX/6.5.30/disc1/dist for Octane2

General table for each IRIX version:
{| class="wikitable"
!IRIX version
!Remote directory
|-
|5.3
|IRIX/irix53/1/dist
|-
|6.2
|IRIX/irix62/1/dist
|-
|6.3
|IRIX/irix63/1/dist
|-
|6.5.0
|IRIX/irix650/1/dist
|-
|6.5.7
|IRIX/irix657/1/dist
|-
|6.5.22
|IRIX/6.5.22/ovl1/dist
|-
|6.5.30
|IRIX/6.5.30/disc1/dist
|}
If asked for system name or IP, specify the name/IP according the netaddr variable in Command Monitor:

IRIS for 192.168.9.1

IRIS2 for 192.168.9.2

Troubleshooting

If the installer program doesn't start, please check:

 1. netaddr is properly configured in Command Monitor.

 2. if the problem persists, connect the target machine to Reanimator using a straight-through cable, not a crossover.

 3. if the problem persists again, attempt to boot the installer program using the "hard way", booting from Command Monitor.

=== Formatting/MKFS on the root partition using Inst installer program ===
Select option "13. admin" --&gt; "11. mkfs" --&gt; (y)es --&gt; yes --&gt; "21. return" (numbers can change depending on the Inst version)


For a 4G disk or smaller, a 512-byte size is recommended. Any larger size, use 4096.

=== Installing IRIX ===
Load the selections file according to the IRIX version installed. Check the right file on Reanimator's main menu, for example:

Use "rbpi" or "debian" according to the installation platform

6.5.22: Select option "13. admin" --&gt; "15. load filename" --&gt; irix@rbpi:i/6.5.22.txt --&gt; "21. return"

6.5.30: Select option "13. admin" --&gt; "15. load filename" --&gt; irix@rbpi:i/6.5.30.txt --&gt; "21. return"

6.5.7: Select option "13. admin" --&gt; "15. load filename" --&gt; irix@rbpi:i/6.5.7.txt --&gt; "21. return"

If there is no selections file for the IRIX version, load the sources manually: select option "1. from [source]" and add the right sources, type "rbpi" or "debian" for server name, SKIP "/" before "i". For example:

Indy: use "rbpi" or "debian" according to the installation platform

irix@rbpi:i/IRIX/6.5.22/ovl1/dist

irix@rbpi:i/IRIX/6.5.22/ovl2/dist

irix@rbpi:i/IRIX/6.5.22/ovl3/dist

irix@rbpi:i/IRIX/6.5.22/apps/dist

irix@rbpi:i/IRIX/irix65x/f1/dist

irix@rbpi:i/IRIX/irix65x/f2/dist

irix@rbpi:i/IRIX/irix65x/nfs/dist

(optional) irix@rbpi:i/IRIX/irix65x/devl/dist

(optional) irix@rbpi:i/IRIX/irix65x/devf13/dist

Octane2: use "rbpi" or "debian" according to the installation platform

irix@rbpi:i/IRIX/6.5.30/disc1/dist

irix@rbpi:i/IRIX/6.5.30/disc2/dist

irix@rbpi:i/IRIX/6.5.30/disc3/dist

irix@rbpi:i/IRIX/6.5.30/apps/dist

irix@rbpi:i/IRIX/6.5.30/capps/dist

irix@rbpi:i/IRIX/irix65x/f1/dist

irix@rbpi:i/IRIX/irix65x/f2/dist

irix@rbpi:i/IRIX/irix65x/nfs/dist

(optional) irix@rbpi:i/IRIX/irix65x/devl/dist

(optional) irix@rbpi:i/IRIX/irix65x/devf13/dist

For IRIX 6.5.7: use "rbpi" or "debian" according to the installation platform

irix@rbpi:i/IRIX/irix657/1/dist

irix@rbpi:i/IRIX/irix657/2/dist

irix@rbpi:i/IRIX/irix657/apps/dist

(optional) irix@rbpi:i/IRIX/irix65x/devf/dist

(optional) irix@rbpi:i/IRIX/irix65x/devl/dist

irix@rbpi:i/IRIX/irix65x/f1/dist

irix@rbpi:i/IRIX/irix65x/f2/dist

irix@rbpi:i/IRIX/irix65x/nfs/dist

Depending on the IRIX version and computer model, the installation procedure can be slightly different. Search videos on Youtube or documentation about IRIX installation on your model.

=== Tested IRIX versions using Reanimator ===
6.5.22 on Indy

6.5.7 on Indy

6.5.30 on Octane2

inst&gt; keep *

inst&gt; install maintenance

inst&gt; conflicts

inst&gt; conflicts 1a 2a ... until no conflicts

inst&gt; go

&lt;nowiki&gt;----------&lt;/nowiki&gt;

6.5.0 on Indy

In this case, selections file won't work, so one must write the sources manually: select option "1. from [source]" and add the right sources, type "rbpi" or "debian" for server name, SKIP "/" before "i". For example:

Use "rbpi" or "debian" according to the installation platform. These are the sources:

irix@rbpi:i/IRIX/irix650/1/dist

irix@rbpi:i/IRIX/irix650/apps/dist

(optional) irix@rbpi:i/IRIX/irix65x/devf/dist

(optional) irix@rbpi:i/IRIX/irix65x/devl/dist

irix@rbpi:i/IRIX/irix65x/f1/dist

irix@rbpi:i/IRIX/irix65x/f2/dist

irix@rbpi:i/IRIX/irix65x/nfs/dist

It will prompt for:

Should it run the optional installation startup script? --&gt; select option 1

Check for kernel crash files ... ? --&gt; answer yes

inst&gt; keep *

inst&gt; install standard

inst&gt; install prereqs

inst&gt; conflicts 1a 2a ... until no conflicts

inst&gt; go

&lt;nowiki&gt;----------&lt;/nowiki&gt;

6.3 (for O2 R5k/R10k) on O2 R5k (tested by kikems). This procedure is similar to IRIX 6.5.0 installation

- select option "1. from [source]" and add the right sources, type "rbpi" or "debian" for server name, SKIP "/" before "i". For example:

Use "rbpi" or "debian" according to the installation platform. These are the sources:

irix@rbpi:i/IRIX/irix63/1/dist

irix@rbpi:i/IRIX/irix63/apps/dist

(optional) irix@rbpi:i/IRIX/irix63/devlib/dist

(optional) irix@rbpi:i/IRIX/irix63/devf/dist

irix@rbpi:i/IRIX/irix63/nfs/dist

The required disk space is ~500 MB and ~890 MB if your include the development sources.

After the installation process:

- select option "12. quit"

- reboot the system

- configure the network with IP address 192.168.9.1 using System --&gt; System Manager --&gt; Network Setup on Toolchest

- add "rbpi 192.168.9.100" to /etc/hosts (I used vi)

- check the rest of directories on /home/irix/i/IRIX/irix63 for patches and additional software:

/home/irix/i/IRIX/irix63/patches/dist

&lt;nowiki&gt;----------&lt;/nowiki&gt;

5.3 on Indy

WARNING: there are several IRIX versions depending on the sgi model, if this version doesn't work, please check other versions on &lt;nowiki&gt;http://jrra.zone/sgi/#pg-7&lt;/nowiki&gt;

- for every source in /home/irix/i/5.3.txt: select option "1. from [source]", add the source and run "go". These are the sources:

irix@rbpi:i/IRIX/irix53/1/dist

irix@rbpi:i/IRIX/irix53/dev53/dist

irix@rbpi:i/IRIX/irix53/gzip/dist

irix@rbpi:i/IRIX/irix53/nfs/dist

After the installation process:

- select option "12. quit"

- reboot the system

- configure the network with IP address 192.168.9.1 using System --&gt; System Manager --&gt; Network Setup on Toolchest

- add "rbpi 192.168.9.100" to /etc/hosts using vi or ed  (no nano or ee)

- check the rest of directories on /home/irix/i/IRIX/irix53 for patches and additional software:

/home/irix/i/IRIX/irix53/patches/dist

/home/irix/i/IRIX/irix53/y2k

&lt;nowiki&gt;----------&lt;/nowiki&gt;

6.2 on Indy. This procedure is similar to IRIX 5.3 installation

- for every source in /home/irix/i/6.2.txt: select option "1. from [source]", add the source and run "go". These are the sources:

irix@rbpi:i/IRIX/irix62/1/dist

irix@rbpi:i/IRIX/irix62/2/dist

irix@rbpi:i/IRIX/irix62/apps/dist

irix@rbpi:i/IRIX/irix62/nfs62/dist

(optional) irix@rbpi:i/IRIX/irix62/devf

(optional) irix@rbpi:i/IRIX/irix62/devlibs

After the installation process:

- select option "12. quit"

- reboot the system

- configure the network with IP address 192.168.9.1 using System --&gt; System Manager --&gt; Network Setup on Toolchest

- add "rbpi 192.168.9.100" to /etc/hosts (I used vi)

- check the rest of directories on /home/irix/i/IRIX/irix62 for patches and additional software:

/home/irix/i/IRIX/irix62/patches/dist

/home/irix/i/IRIX/irix62/y2k_patch</text>
    <sha1>86c2f70ad1e65127e5355aa6ad25db0d4cef2956</sha1>
  </revision>
  <revision>
    <id>278</id>
    <parentid>277</parentid>
    <timestamp>2025-02-22T16:49:58Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Base setup</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9527" xml:space="preserve">Reanimator is a specially created Linux VM for Virtualbox and Raspberry Pi systems. It can install IRIX on most systems. 

This guide is derived from their official documentation. It will be different from other [[Installing IRIX]] guides

=== Setting IP client address in Command Monitor ===
To enter Comand Monitor, boot the target machine and click on "Stop for Maintenance dialog" or press Esc. Click on "Enter Command Monitor" or press "5" (on Indy, numbers can change on other sgi model).

Two IP client addresses are available:

IRIS: setenv netaddr 192.168.9.1

or

IRIS2: setenv netaddr 192.168.9.2

To reboot from disk 1 after the installation, run in Command Monitor:
 &lt;code&gt;&gt;&gt;setenv SystemPartition dksc(0,1,8)
 &gt;&gt;setenv OSLoadPartition dksc(0,1,0)
 &gt;&gt;setenv OSLoader sash
 &gt;&gt;setenv OSLoadFilename unix&lt;/code&gt;

=== Starting the partition tool in Command Monitor ===
Examples on how to start fx, the partitioning tool:
IRIX systems using a 32-bit kernel (e.g. any pre-ARCS SGIs, the Indy, O2, Indigo2 R4000 etc.) use fx.ARCS, all others use fx.64


32-bits:

bootp():IRIX/6.5.22/ovl1/stand/fx.ARCS -x

bootp():IRIX/irix53/1/stand/fx.ARCS -x

bootp():IRIX/irix62/1/stand/fx.ARCS -x

bootp():IRIX/irix650/1/stand/fx.ARCS -x

bootp():IRIX/irix657/1/stand/fx.ARCS -x

64-bits:

bootp():IRIX/6.5.30/disc1/stand/fx.64 -x

bootp():IRIX/irix650/1/stand/fx.64 -x

bootp():IRIX/irix657/1/stand/fx.64 -x

=== Creating a disklabel ===
A disklabel cannot format the contents of a drive. Unlike MS Windows, a format command in UNIX is mkfs. This will be 

covered later. 

Press Enter a couple of times to select the default system disk on SCSI controller 0, ID 1, lun 0

fx&gt; [l]abel

fx/label&gt; [c]reate

fx/label/create&gt; [a]ll

fx/label/create&gt; ..

fx/label&gt; [sy]nc

fx/label&gt; ..

fx&gt; [r]epartition

fx/repartition&gt; [ro]otdrive

fx/repartition/rootdrive: type of data partition = (xfs)

fx/repartition&gt; /exit

=== Starting the installer from network ===
- Enter System Maintenance menu, press 2 or click on "Install system software"

- Press 2 or click on "From remote directory"

- Enter "rbpi" or "debian" (according to the installation platform) as "server name", NOT the IP address

- For example:

Indy:

IRIX/6.5.22/ovl1/dist

Octane2:

IRIX/6.5.30/disc1/dist for Octane2

General table for each IRIX version:
{| class="wikitable"
!IRIX version
!Remote directory
|-
|5.3
|IRIX/irix53/1/dist
|-
|6.2
|IRIX/irix62/1/dist
|-
|6.3
|IRIX/irix63/1/dist
|-
|6.5.0
|IRIX/irix650/1/dist
|-
|6.5.7
|IRIX/irix657/1/dist
|-
|6.5.22
|IRIX/6.5.22/ovl1/dist
|-
|6.5.30
|IRIX/6.5.30/disc1/dist
|}
If asked for system name or IP, specify the name/IP according the netaddr variable in Command Monitor:

IRIS for 192.168.9.1

IRIS2 for 192.168.9.2

Troubleshooting

If the installer program doesn't start, please check:

 1. netaddr is properly configured in Command Monitor.

 2. if the problem persists, connect the target machine to Reanimator using a straight-through cable, not a crossover.

 3. if the problem persists again, attempt to boot the installer program using the "hard way", booting from Command Monitor.

=== Formatting/MKFS on the root partition using Inst installer program ===
Select option "13. admin" --&gt; "11. mkfs" --&gt; (y)es --&gt; yes --&gt; "21. return" (numbers can change depending on the Inst version)


For a 4G disk or smaller, a 512-byte size is recommended. Any larger size, use 4096.

=== Installing IRIX ===
Load the selections file according to the IRIX version installed. Check the right file on Reanimator's main menu, for example:

Use "rbpi" or "debian" according to the installation platform

6.5.22: Select option "13. admin" --&gt; "15. load filename" --&gt; irix@rbpi:i/6.5.22.txt --&gt; "21. return"

6.5.30: Select option "13. admin" --&gt; "15. load filename" --&gt; irix@rbpi:i/6.5.30.txt --&gt; "21. return"

6.5.7: Select option "13. admin" --&gt; "15. load filename" --&gt; irix@rbpi:i/6.5.7.txt --&gt; "21. return"

If there is no selections file for the IRIX version, load the sources manually: select option "1. from [source]" and add the right sources, type "rbpi" or "debian" for server name, SKIP "/" before "i". For example:

Indy: use "rbpi" or "debian" according to the installation platform

irix@rbpi:i/IRIX/6.5.22/ovl1/dist

irix@rbpi:i/IRIX/6.5.22/ovl2/dist

irix@rbpi:i/IRIX/6.5.22/ovl3/dist

irix@rbpi:i/IRIX/6.5.22/apps/dist

irix@rbpi:i/IRIX/irix65x/f1/dist

irix@rbpi:i/IRIX/irix65x/f2/dist

irix@rbpi:i/IRIX/irix65x/nfs/dist

(optional) irix@rbpi:i/IRIX/irix65x/devl/dist

(optional) irix@rbpi:i/IRIX/irix65x/devf13/dist

Octane2: use "rbpi" or "debian" according to the installation platform

irix@rbpi:i/IRIX/6.5.30/disc1/dist

irix@rbpi:i/IRIX/6.5.30/disc2/dist

irix@rbpi:i/IRIX/6.5.30/disc3/dist

irix@rbpi:i/IRIX/6.5.30/apps/dist

irix@rbpi:i/IRIX/6.5.30/capps/dist

irix@rbpi:i/IRIX/irix65x/f1/dist

irix@rbpi:i/IRIX/irix65x/f2/dist

irix@rbpi:i/IRIX/irix65x/nfs/dist

(optional) irix@rbpi:i/IRIX/irix65x/devl/dist

(optional) irix@rbpi:i/IRIX/irix65x/devf13/dist

For IRIX 6.5.7: use "rbpi" or "debian" according to the installation platform

irix@rbpi:i/IRIX/irix657/1/dist

irix@rbpi:i/IRIX/irix657/2/dist

irix@rbpi:i/IRIX/irix657/apps/dist

(optional) irix@rbpi:i/IRIX/irix65x/devf/dist

(optional) irix@rbpi:i/IRIX/irix65x/devl/dist

irix@rbpi:i/IRIX/irix65x/f1/dist

irix@rbpi:i/IRIX/irix65x/f2/dist

irix@rbpi:i/IRIX/irix65x/nfs/dist

Depending on the IRIX version and computer model, the installation procedure can be slightly different. Search videos on Youtube or documentation about IRIX installation on your model.

=== Tested IRIX versions using Reanimator ===
6.5.22 on Indy

6.5.7 on Indy

6.5.30 on Octane2

inst&gt; keep *

inst&gt; install maintenance

inst&gt; conflicts

inst&gt; conflicts 1a 2a ... until no conflicts

inst&gt; go

&lt;nowiki&gt;----------&lt;/nowiki&gt;

6.5.0 on Indy

In this case, selections file won't work, so one must write the sources manually: select option "1. from [source]" and add the right sources, type "rbpi" or "debian" for server name, SKIP "/" before "i". For example:

Use "rbpi" or "debian" according to the installation platform. These are the sources:

irix@rbpi:i/IRIX/irix650/1/dist

irix@rbpi:i/IRIX/irix650/apps/dist

(optional) irix@rbpi:i/IRIX/irix65x/devf/dist

(optional) irix@rbpi:i/IRIX/irix65x/devl/dist

irix@rbpi:i/IRIX/irix65x/f1/dist

irix@rbpi:i/IRIX/irix65x/f2/dist

irix@rbpi:i/IRIX/irix65x/nfs/dist

It will prompt for:

Should it run the optional installation startup script? --&gt; select option 1

Check for kernel crash files ... ? --&gt; answer yes

inst&gt; keep *

inst&gt; install standard

inst&gt; install prereqs

inst&gt; conflicts 1a 2a ... until no conflicts

inst&gt; go

&lt;nowiki&gt;----------&lt;/nowiki&gt;

6.3 (for O2 R5k/R10k) on O2 R5k (tested by kikems). This procedure is similar to IRIX 6.5.0 installation

- select option "1. from [source]" and add the right sources, type "rbpi" or "debian" for server name, SKIP "/" before "i". For example:

Use "rbpi" or "debian" according to the installation platform. These are the sources:

irix@rbpi:i/IRIX/irix63/1/dist

irix@rbpi:i/IRIX/irix63/apps/dist

(optional) irix@rbpi:i/IRIX/irix63/devlib/dist

(optional) irix@rbpi:i/IRIX/irix63/devf/dist

irix@rbpi:i/IRIX/irix63/nfs/dist

The required disk space is ~500 MB and ~890 MB if your include the development sources.

After the installation process:

- select option "12. quit"

- reboot the system

- configure the network with IP address 192.168.9.1 using System --&gt; System Manager --&gt; Network Setup on Toolchest

- add "rbpi 192.168.9.100" to /etc/hosts (I used vi)

- check the rest of directories on /home/irix/i/IRIX/irix63 for patches and additional software:

/home/irix/i/IRIX/irix63/patches/dist

&lt;nowiki&gt;----------&lt;/nowiki&gt;

5.3 on Indy

WARNING: there are several IRIX versions depending on the sgi model, if this version doesn't work, please check other versions on &lt;nowiki&gt;http://jrra.zone/sgi/#pg-7&lt;/nowiki&gt;

- for every source in /home/irix/i/5.3.txt: select option "1. from [source]", add the source and run "go". These are the sources:

irix@rbpi:i/IRIX/irix53/1/dist

irix@rbpi:i/IRIX/irix53/dev53/dist

irix@rbpi:i/IRIX/irix53/gzip/dist

irix@rbpi:i/IRIX/irix53/nfs/dist

After the installation process:

- select option "12. quit"

- reboot the system

- configure the network with IP address 192.168.9.1 using System --&gt; System Manager --&gt; Network Setup on Toolchest

- add "rbpi 192.168.9.100" to /etc/hosts using vi or ed  (no nano or ee)

- check the rest of directories on /home/irix/i/IRIX/irix53 for patches and additional software:

/home/irix/i/IRIX/irix53/patches/dist

/home/irix/i/IRIX/irix53/y2k

&lt;nowiki&gt;----------&lt;/nowiki&gt;

6.2 on Indy. This procedure is similar to IRIX 5.3 installation

- for every source in /home/irix/i/6.2.txt: select option "1. from [source]", add the source and run "go". These are the sources:

irix@rbpi:i/IRIX/irix62/1/dist

irix@rbpi:i/IRIX/irix62/2/dist

irix@rbpi:i/IRIX/irix62/apps/dist

irix@rbpi:i/IRIX/irix62/nfs62/dist

(optional) irix@rbpi:i/IRIX/irix62/devf

(optional) irix@rbpi:i/IRIX/irix62/devlibs

After the installation process:

- select option "12. quit"

- reboot the system

- configure the network with IP address 192.168.9.1 using System --&gt; System Manager --&gt; Network Setup on Toolchest

- add "rbpi 192.168.9.100" to /etc/hosts (I used vi)

- check the rest of directories on /home/irix/i/IRIX/irix62 for patches and additional software:

/home/irix/i/IRIX/irix62/patches/dist

/home/irix/i/IRIX/irix62/y2k_patch

[[Category:No-Images]]
[[Category:Tutorials]]</text>
    <sha1>95210f9f7e2859b4a4ce437f853845d3dc071d53</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Open Source Software</title>
  <ns>0</ns>
  <id>114</id>
  <revision>
    <id>279</id>
    <parentid>215</parentid>
    <timestamp>2025-02-22T17:15:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="360" xml:space="preserve">SGI and the community have offered several flavors of "ware" for IRIX. A list of them and what they focus on is here. 

=== For IRIX 6.5 ===
[[IRIX 6.5]] by far has the most editions of software for it. 

=== For 6.2/5.3 ===
[http://tgcware.irixnet.org/ TGCWare] has set the bar for this. As it has been frozen since the 2010s, we linked to the IRIXNet mirror.</text>
    <sha1>3baeabc683302eefba3bc8d4749b1d039cc82bf1</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>File:Silicon Graphics International logo.png</title>
  <ns>6</ns>
  <id>135</id>
  <revision>
    <id>280</id>
    <timestamp>2025-02-22T17:22:26Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="44" xml:space="preserve">The "SGI" logo from the Rackable Systems era</text>
    <sha1>8445c721dc54fb7742ca6c15480ece659a44cc29</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Rackable Systems</title>
  <ns>0</ns>
  <id>136</id>
  <revision>
    <id>281</id>
    <timestamp>2025-02-22T17:23:11Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Silicon Graphics International logo.png|thumb|The "SGI" logo from the Rackable Systems era]] '''Rackable Systems''', later known by '''Silicon Graphics International''' (Not to be confused with the original [[Silicon Graphics]]) was a company founded in 1999 in San Jose, CA. During SGI's bankruptcy, Rackable emerged as the victor and assumed the identity of the company soon after. As an x86-based server company, the company quickly winded down [[Itanium]] and MI..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="946" xml:space="preserve">[[File:Silicon Graphics International logo.png|thumb|The "SGI" logo from the Rackable Systems era]]
'''Rackable Systems''', later known by '''Silicon Graphics International''' (Not to be confused with the original [[Silicon Graphics]]) was a company founded in 1999 in San Jose, CA. During SGI's bankruptcy, Rackable emerged as the victor and assumed the identity of the company soon after. As an x86-based server company, the company quickly winded down [[Itanium]] and [[MIPS]] system development, completing this around 2013. Most of its products were x86-based, NUMA enabled systems. 

In 2016, Hewlett Packard Enterprise, a historical competitor to the original SGI, purchased Rackable Systems and all assets. 

=== Operations after Acquiring SGI ===
After acquisition, Rackable used SGI branding, especially the "Altix" series for its x86-based systems. These systems were called Altix UV systems.

[[Category:Stubs]]
[[Category:Companies]]</text>
    <sha1>0ec8b9d2f405c8b14d54e76114c4fa2b0a2a83e4</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>File:Sgi later logo.png</title>
  <ns>6</ns>
  <id>137</id>
  <revision>
    <id>282</id>
    <timestamp>2025-02-22T17:24:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="35" xml:space="preserve">Later logo of Silicon Graphics Inc.</text>
    <sha1>19d54019ec5fcb9700eb603a7b0a1c56926958e9</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Silicon Graphics</title>
  <ns>0</ns>
  <id>138</id>
  <revision>
    <id>283</id>
    <timestamp>2025-02-22T17:24:49Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Sgi later logo.png|thumb|Later logo of Silicon Graphics Inc.]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="69" xml:space="preserve">[[File:Sgi later logo.png|thumb|Later logo of Silicon Graphics Inc.]]</text>
    <sha1>94060e3cda45045d2b15697f8039322c93a60799</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>MIPS</title>
  <ns>0</ns>
  <id>139</id>
  <revision>
    <id>284</id>
    <timestamp>2025-02-22T17:37:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "'''MIPS''', standing for "'''Microprocessor without Interlocked Pipelined Stages'''" is a RISC CPU architecture developed firstly by MIPS Computer Systems, then later [[Silicon Graphics]], and now by MIPS Technologies. MIPS is derived from the Stanford RISC project and mostly conforms to the basic design conventions of that standard.   === History === The first version of the MIPS CPU was the R2000 microprocessor, released in 1985. MIPS Computer Systems used the R2000 as..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2380" xml:space="preserve">'''MIPS''', standing for "'''Microprocessor without Interlocked Pipelined Stages'''" is a RISC CPU architecture developed firstly by MIPS Computer Systems, then later [[Silicon Graphics]], and now by MIPS Technologies. MIPS is derived from the Stanford RISC project and mostly conforms to the basic design conventions of that standard. 

=== History ===
The first version of the MIPS CPU was the R2000 microprocessor, released in 1985. MIPS Computer Systems used the R2000 as the main CPU for their systems running [[RISC/OS]].

=== ISA ===
MIPS began in 1985 with the MIPS I standard, then later MIPS II, III and IV were released as iterations upon the same architecture. MIPS is a load/store architecture (also known as a ''register-register architecture''); except for the load/store instructions used to access memory, all instructions operate on the registers.

==== MIPS I ====
MIPS I has thirty-two 32-bit general-purpose registers. Register $0 is hardwired to zero and writes to it are discarded. Register $31 is the link register. For integer multiplication and division instructions, which run asynchronously from other instructions, a pair of 32-bit registers, ''HI'' and ''LO'', are provided. There is a small set of instructions for copying data between the general-purpose registers and the HI/LO registers.

The program counter has 32 bits. The two low-order bits always contain zero since MIPS I instructions are 32 bits long and are aligned to their natural word boundaries.

==== Instruction formats ====
Instructions are divided into three types: R (register), I (immediate), and J (jump). Every instruction starts with a 6-bit opcode. In addition to the opcode, R-type instructions specify three registers, a shift amount field, and a function field; I-type instructions specify two registers and a 16-bit immediate value; J-type instructions follow the opcode with a 26-bit jump target.

The following are the three formats used for the core instruction set:
{| class="wikitable"
!Type
! colspan="6" |-31-                                 format (bits)                                 -0-
|-
|'''R'''
|opcode (6)
|rs (5)
|rt (5)
|rd (5)
|shamt (5)
|funct (6)
|-
|'''I'''
|opcode (6)
|rs (5)
|rt (5)
| colspan="3" |immediate (16)
|-
|'''J'''
|opcode (6)
| colspan="5" |address (26)
|}

[[Category: No-Images]]
[[Category: Stubs]]</text>
    <sha1>7ff8344ee7fc70b4b29e3a04597890f8c455ecfe</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Itanium</title>
  <ns>0</ns>
  <id>109</id>
  <revision>
    <id>285</id>
    <parentid>174</parentid>
    <timestamp>2025-02-22T17:49:32Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1803" xml:space="preserve">Itanium, also known as IA-64 and IPF (Itanium Processor Family), is a RISC-like CPU architecture developed by HPE and Intel in the 1990s to serve as a high end, 64-bit, RISC processor architecture to replace HP's PA-RISC. Incidentally, SGI also adopted it to replace [[MIPS]] due to being unable to continue MIPS development due to early 2000s financial difficulties. 

=== History of Itanium ===
In 1989 the Fort Collins Design Center, a part of Hewlett Packard, but now a part of Intel, began work on a new RISC architecture to exceed the performance of current RISC iterations. Intel joined the alliance in 1994 and quickly became the face of Itanium. 

Due to delays and development hell, the 1997-1998 launch window was missed and Merced, the initial Itanium design, only began shipping volume around 2001. At that time, Merced was neither competitive or impressive. This, combined with continued delays of Itanium 2, negative press from consumer publications misunderstanding Itanium's purpose (It was never designed to replace x86) and mismanagement led many partners to evacuate the Itanium alliance. 

By 2005, IBM, Sun, Dell and many others had mostly evacuated the Itanium alliance, leaving HP and several Japanese companies (e.g. Hitachi) as Intel's primary customer. SGI shipped Itanium, but not in sufficient volume, and by 2008 SGI declared bankruptcy. 

=== Design ===
Itanium uses the EPIC (Explicitly Parallel Instruction Computing), but internally it resembles the Berkeley RISC design, with register windowing, in-order opcode loading, mostly fixed length instructions, etc. It differs from traditional RISC in using VLIW-like instruction bundling to enable parallel execution. It additionally had 64-bit SIMD instructions, similar to MMX.

[[Category:Stubs]]
[[Category:Processors]]</text>
    <sha1>e9a0d6caa59a822d4f274ea91789dd2e4a3d9c8a</sha1>
  </revision>
  <revision>
    <id>287</id>
    <parentid>285</parentid>
    <timestamp>2025-02-22T17:50:36Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1883" xml:space="preserve">[[File:Intel Itanium Logo.png|thumb|Explicitly parallel instruction computing]]
Itanium, also known as IA-64 and IPF (Itanium Processor Family), is a RISC-like CPU architecture developed by HPE and Intel in the 1990s to serve as a high end, 64-bit, RISC processor architecture to replace HP's PA-RISC. Incidentally, SGI also adopted it to replace [[MIPS]] due to being unable to continue MIPS development due to early 2000s financial difficulties. 

=== History of Itanium ===
In 1989 the Fort Collins Design Center, a part of Hewlett Packard, but now a part of Intel, began work on a new RISC architecture to exceed the performance of current RISC iterations. Intel joined the alliance in 1994 and quickly became the face of Itanium. 

Due to delays and development hell, the 1997-1998 launch window was missed and Merced, the initial Itanium design, only began shipping volume around 2001. At that time, Merced was neither competitive or impressive. This, combined with continued delays of Itanium 2, negative press from consumer publications misunderstanding Itanium's purpose (It was never designed to replace x86) and mismanagement led many partners to evacuate the Itanium alliance. 

By 2005, IBM, Sun, Dell and many others had mostly evacuated the Itanium alliance, leaving HP and several Japanese companies (e.g. Hitachi) as Intel's primary customer. SGI shipped Itanium, but not in sufficient volume, and by 2008 SGI declared bankruptcy. 

=== Design ===
Itanium uses the EPIC (Explicitly Parallel Instruction Computing), but internally it resembles the Berkeley RISC design, with register windowing, in-order opcode loading, mostly fixed length instructions, etc. It differs from traditional RISC in using VLIW-like instruction bundling to enable parallel execution. It additionally had 64-bit SIMD instructions, similar to MMX.

[[Category:Stubs]]
[[Category:Processors]]</text>
    <sha1>d32625dc274c077b61aa0ce0c142e1843d589bb6</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>File:Intel Itanium Logo.png</title>
  <ns>6</ns>
  <id>140</id>
  <revision>
    <id>286</id>
    <timestamp>2025-02-22T17:50:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="34" xml:space="preserve">Intel's marketing logo for Itanium</text>
    <sha1>c8841d2f4dee6631dd9eff010662516ff75ffa6b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Packaging Software For Nekoware</title>
  <ns>0</ns>
  <id>141</id>
  <revision>
    <id>288</id>
    <timestamp>2025-02-23T00:46:55Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "'''This is a draft. Do not follow it for advice'''  == Package Format - tardist == IRIX packages are called ''tardists'' and, as the name implies, are essentially tar(1)'ed sets of distribution files. These files describe the location and permissions of all files related to a particular piece of software. These tardists can then be distributed and installed on similarly-configured SGI machines.  == Tools Required ==  === Compilers === For IRIX, the system compiler is kno..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20332" xml:space="preserve">'''This is a draft. Do not follow it for advice'''

== Package Format - tardist ==
IRIX packages are called ''tardists'' and, as the name implies, are essentially tar(1)'ed sets of distribution files. These files describe the location and permissions of all files related to a particular piece of software. These tardists can then be distributed and installed on similarly-configured SGI machines.

== Tools Required ==

=== Compilers ===
For IRIX, the system compiler is known in 6.5 and 6.2 as [[MIPSPro]], and earlier versions as [[IRIS Development Option]]. For SGI software, there are two viable options:

'''MIPSPro (c99/cc/CC)''': Caveats are that thread local storage is not supported, C11 and C++11 and up features are mostly absent, IRIX's CC (c++) compiler has some important limitations and that cross-compilation is not possible. GCC and MIPSPro are C-ABI compatible, but not C++. MIPSPro is fast at compilation, uses less memory, and can potentially improve performance 

'''GCC''': Caveats are that applications that use native C++ libs (libfam, libviewkit, libinst) etc. cannot be built under GCC. They won't link correctly. Link-time optimization and thread local storage do not work correctly on IRIX, SGUG RSE disables the latter and the former will break binaries. GCC has trouble linking under RSE to pthread and GL libs, and pthread libraries otherwise. GNU binutils has limitations, and most GCC will only build 32-bit apps correctly. 

=== Platform ===
In order to build software for Nekoware, it's recommended to run IRIX 6.5.21 or newer, have at least 512M RAM, and an R10000 at 175MHz or an R5200 at 300MHz or greater. Nekoware does not support cross compilation, but these machines are fast enough to not require it.

=== Software ===
MIPSPro requires a license. [[Flexlm]] licenses exist for it, but it can also be patched to remove the check. GNU make 3.81 or later is also recommended, as IRIX pmake, smake and make are all unsuitable for modern software. 

== Build Environment ==
Be sure to set some global variables for development on IRIX. The following is a set of sensible starting point. setenv(1) is used on tcsh, export for KSH and GNU Bash:&lt;pre&gt;setenv CC c99

setenv CXX CC

setenv CFLAGS '-O2 -mips4 -TARG:proc=r10000'

setenv CXXFLAGS '-O2 -mips4 -TARG:proc=r10000'

setenv CPPFLAGS '-I/usr/nekoware/include -I/usr/include'

setenv LDFLAGS '-L/usr/nekoware/lib32 -L/usr/lib32 -Wl,-rpath -Wl,/usr/nekoware/lib32'

setenv PKG_CONFIG '/usr/nekoware/bin/pkgconf'

setenv PKG_CONFIG_PATH '/usr/nekoware/lib32/pkgconfig'

setenv ACLOCAL_PATH '/usr/nekoware/share/aclocal'&lt;/pre&gt;&lt;pre&gt;
export CC=c99

export CXX=CC

export CFLAGS='-O2 -mips4 -TARG:proc=r10000'

export CXXFLAGS='-O2 -mips4 -TARG:proc=r10000'

export CPPFLAGS='-I/usr/nekoware/include -I/usr/include'

export LDFLAGS='-L/usr/nekoware/lib32 -L/usr/lib32 -Wl,-rpath -Wl,/usr/nekoware/lib32'

export PKG_CONFIG='/usr/nekoware/bin/pkgconf'

export PKG_CONFIG_PATH='/usr/nekoware/lib32/pkgconfig'

export ACLOCAL_PATH='/usr/nekoware/share/aclocal'
&lt;/pre&gt;All Nekoware is installed relative to /usr/nekoware and should be built and linked against the libraries there. 

Furthermore, there are some MIPSpro options that should be set:

Defining &lt;code&gt;CC&lt;/code&gt; and &lt;code&gt;CXX&lt;/code&gt; specifies the MIPSpro compiler suite. The &lt;code&gt;CFLAGS&lt;/code&gt; option indicates building for MIPS IV, that being any MIPS processor R5000 or newer (see above).

Also present are additional optimizations being done for the R10000 platform (more specifically the SGI Origin 200 IP27), which is a common processor among the SGI O2, SGI Octane, and SGI Origin platforms. This build will work on R5000, but will see additional optimization on R10000 or better. If the software is optimization-friendly, e.g. mplayer or blender - it is possible to provide different builds, optimized for specific processors and have inst or swmgr automatically select the best build during installation.

Alternatively, the &lt;code&gt;-TARG&lt;/code&gt; option could be disgarded entirely to build without any platform-specific optimizations whatsoever. Many Nekoware packages use only &lt;code&gt;-03 -mips4&lt;/code&gt;.

Note: A great deal of open source software expects the compiler suite to halt processing if an "#error" preprocessor directive is encountered. GCC does this, while MIPSpro does not by default. To get this behavior with MIPSpro you can add "-diag_error 1035" to the CFLAGS definition above.

== Creating a Sandbox ==
Typically, a location under the home directory would be used for holding source tarballs, build directories and other working files. Under this directory, creating '''two''' copies of the build directory will aid the patch creation process later on. Suppose one were building fooware, version 1.2.3, within this working directory:
 (prompt) gunzip -c fooware-1.2.3.tar.gz | tar xf -
 (prompt) cp -r fooware-1.2.3 fooware-1.2.3-PATCHED
There are now two identical versions of the source directory. By maintaining the original source and working within the "-PATCHED" directory, creating a patch for the package will be much more simple.

== Building the Software ==
Typically, after a sandbox has been created, the software should be configured from within the "-PATCHED" directory (following the directions above). Remember, all Nekoware packages are installed relative to /usr/nekoware, so the &lt;code&gt;--prefix&lt;/code&gt; option should be passed to configure. libdir must be done as well, as /lib is for o32 software and /lib64 for 64-bit
 % ./configure --prefix=/usr/nekoware --libdir=/usr/lib32
Be sure to specify any other configure arguments necessary to build the software. It may be necessary to write down any dependencies configure checks to create accurate rules later.

After the software has been successfully configured, compile the source as usual. As an example, something like this might be used to compile the software on a dual-processor machine:
 % gmake -j3
If the software successfully compiled, it may be possible to simply run the software from within the working directory, without installing anything. If so, try that now and verify that all desired functionality is present. If not, the software should now be installed using something similar to the following:&lt;pre&gt;
% sudo -s
% gmake install
% exit
&lt;/pre&gt;After installation, test the software as above to verify the successful build.

== Installing the Software ==
To package, after confirming build and install correctly, reconfigure the software to install to a staging directory:&lt;pre&gt;
./configure --prefix=/usr/neko_staging --libdir=/usr/neko_staging/lib32
&lt;/pre&gt;This will allow tracing by either swpkg(1) or genidb(1) to be useful. 

== Package Preparation ==

=== Directory Structure ===
Nekoware packages use a consistent directory structure for patches, sources, release notes and distribution files. Create this structure under the /tmp/build directory (created above), now:
 % mkdir /usr/neko_staging/patches
 % mkdir /usr/neko_staging/src
 % mkdir /usr/neko_staging/relnotes
 % mkdir /usr/neko_staging/dist
Copy the original source distribution and the patch file to their respective directory:
 % cp neko_fooware-1.2.3_irix.patch /usr/neko_staging/patches
 % cp fooware-1.2.3.tar.gz /usr/neko_staging/src

=== Release Notes ===
This section is under construction

== Creating a Package ==
Now that the temporary directory contains the binary software, the source code, the patch and a release notes file, create a distribution directory and run Software Packager:
 % mkdir /usr/neko_dist &amp;&amp;  cd /usr/neko_dist
 % swpkg
The Software Packager interface is designed to be intuitive. The other option will discussed soon. 

== Creating a Product Hierarchy using swpkg ==
On the first worksheet, a tree is displayed showing a default arrangement of subsystems within a package. This may, or may not, suit the software's layout, but it is provided as a starting point for creating a new package.

The first step is to give the package a name on the root node. Something like neko_fooware is recommended. Add a description to this node on the right using other packages in the Software Manager as a guide. '''Be sure to save any changes or they will be lost.'''

Create the other nodes according to the typical Nekoware hierarchy, as follows:
 neko_fooware.eoe (binaries and files for execution only)
 neko_fooware.include (headers)
 neko_fooware.lib (shared libraries)
 neko_fooware.man.manpages (manual pages)
 neko_fooware.opt.src (the original source tarball, this is optional)
 neko_fooware.opt.patches (patches against the original source)
 neko_fooware.opt.relnotes (release notes for this package)
 neko_fooware.opt.dist (distribution files, generated by swpkg)
Not all of the tree may be required by the software. Use common sense and other Nekoware package as a guide.

=== Versioning ===
Every package will have two version numbers that should never be confused: the package version and the software version.

The package version is assigned to all children of the root node on the first worksheet of the Software Packager. This number is incremented for each build of this package independently of the software version contained within the package.

For Nekoware, start a package version at 100. This is because historical nekoware may conflict, which can break things. 

'''Remember: a package's version is independent of the version of the software it contains.'''

Also, ''all'' package version numbers must be equal within a package. If, for example, the execution-only subsystem has changed in a new package, all other subsystem's must have the version numbers incremented, as well. This holds true even if no other subsystems have changed between package versions.

=== Dependencies ===
This is, perhaps, the most important portion of the packaging process and is the reason for recording the software's dependencies during the build stage above. Find the ''package version'' of each dependency using the versions(1) command. For example:
 (prompt) versions -n neko_foo
 (prompt) versions -n neko_bar
 (prompt) versions -n neko_baz 
Each versions(1) command will output several lines, one for each subsystem in the package. Write down the version numbers for each subsystem the software depends on. Be sure to be specific: which subsystem does the software depend on? Just the shared libraries, or the execution environment? Both?

Now, in Software Packager, specify the dependencies for each subsystem in the ''Rules'' section. The rules will look somewhat like the following:
 replaces self
 prereq (
   neko_fooware.lib 100 maxint
   neko_foo.lib 100 maxint
   neko_bar.eoe 100 maxint
   neko_baz.include 100 maxint
 )

=== Final Steps ===
There is also an "install by default" checkbox that should be checked for any subsystems that require it. Typically, the sw.eoe, sw.lib, sw.hdr and man.manpages will have this option checked.

Before continuing, be sure to save the .spec and .idb files that Software Packager creates to /usr/neko_staging/dist. This will make them available to the next step.

== Headless Alternative to swpkg, genidb ==
Running an SGI headless? No problem! Raion and EasyMode developed genidb(1). It skips many of these steps. 

Referencing the above section, start with a spec file. Here's one for fooware, using all of the above steps:&lt;pre&gt;
product neko_fooware
    id "Your description goes here"
    image eoe
        id "fooware binaries"
        version 100
        order 9999
        subsys base default
            id "fooware binaries"
            prereq ( 
            neko_fooware.lib 100 maxint 
            neko_foo.lib 100 maxint 
            neko_bar.eoe 100 maxint 
            neko_baz.include 100 maxint 
            )
            replaces self
            exp neko_fooware.eoe.base
        endsubsys
    endimage
    image lib
        id "fooware libs"
        version 100
        order 9999
        subsys base default
            id "fooware libs"
            prereq ( 
            neko_fooware.lib 100 maxint 
            neko_foo.lib 100 maxint 
            neko_bar.eoe 100 maxint 
            neko_baz.include 100 maxint 
            )
            replaces self
            exp neko_fooware.lib.base
        endsubsys
    endimage
    image include
        id "fooware headers"
        version 100
        order 9999
        subsys base default
            id "fooware headers"
            replaces self
            exp neko_fooware.includes.base
        endsubsys
    endimage
   image man
        id "fooware manpages"
        version 100
        order 9999
        subsys manpages default
            id "fooware manpages"
            replaces self
            exp neko_fooware.man.manpages
        endsubsys
    endimage
    image opt
        id "optional"
        version 1
        order 9999
        subsys patch
            id "patch files"
            replaces self
            exp neko_fooware.opt.patch
        endsubsys
        subsys relnotes
            id "release notes"
            replaces self
            exp neko_fooware.opt.relnotes
        endsubsys
        subsys dist
            id "distribution files"
            replaces self
            exp neko_fooware.opt.dist
        endsubsys
    endimage
endproduct
&lt;/pre&gt;If this looks complicated, just go section by section. If problems still exist, ask on the IRIXNet forums. 

Once that's established, copy it to /usr/neko_staging/dist, add all other files including patches, relnotes etc. 

Then:&lt;pre&gt;
genidb -p /usr/neko_staging -s /usr/neko_staging/dist/neko_fooware.spec -v
&lt;/pre&gt;The output should say:&lt;pre&gt;
(-s) Input Spec: /usr/neko_staging/dist/neko_fooware.spec
(-p) Path: /usr/neko_staging
Working through specified path: /usr/neko_staging
IDB output file: /usr/neko_staging/dist/neko_fooware.spec
Parsed Spec File
Scanning files in: /usr/neko_staging
Completed with 25 entries and 0 rejections. 
&lt;/pre&gt;Or something to this effect. It'll tag files as best it can. Manually review the file, as sometimes subsystems get messed around with. Skip the next section, Tagging. 

==== Building the package ====
Next, the idb must be sorted per the gendist manual:

&lt;code&gt;sort +4u -6 &lt; neko_fooware.idb &gt; /usr/nekoware/dist/neko_fooware.idb&lt;/code&gt;

This will copy it to /usr/nekoware/dist. cp the spec file, patches, relnotes and src if present. 

Next, fix the paths in idb: &lt;code&gt;perl -pi -e 's/_staging/ware/g' neko_fooware.idb&lt;/code&gt;

==== Running Gendist ====
Finally, try gendist:&lt;pre&gt;
% cd /usr/neko_dist

% gendist -sbase / -spec /usr/nekoware/dist/neko_fooware.spec -idb /usr/nekoware/dist/neko_fooware.idb -distdir .
&lt;/pre&gt;It'll give any errors such as empty subsystems and such. 

Skip to Quickstarting for relevant info. 

== Tagging ==
Every file that the software creates and installs must be tagged with a particular subsystem within the package. Above, we created a clean application tree in /tmp/build for this very purpose. Had we not, each file that the software installed would need to be found in /usr/nekoware - a very tedious process!

Import the entire /tmp/build directory and tag each file. For example, files installed in lib/ would be tagged with sw.lib, those in bin/ and share/ should be in sw.eoe and include/ is tagged with sw.hdr.

All directory entries should be removed from the distribution entirely. Leaving them is considered sloppy and clutters the package.

Set all files as owned by the ''root'' user and ''sys'' group, save the .spec and .idb files once more and exit Software Packager.

== Fixing Paths ==
The current package now contains all files installed by the software with the correct permissions and tagged with the correct subsystem. However, due to using the sandbox, /tmp/build, all of the paths are incorrect. Thankfully, correcting them is an easy proposition:
 (prompt) cat /tmp/build/usr/nekoware/dist/neko_fooware.idb | \
 sed 's/\/tmp\/build//g' &gt; tmp.idb
 (prompt) mv tmp.idb /tmp/build/usr/nekoware/dist/neko_fooware.idb
Alternatively, the .idb file can be opened using a text editor and the necessary replacements done using the editor's find-and-replace functionality.

Re-launch the Software Packager and open the .spec and .idb files. Verify that the paths are correct.

== Quickstarting ==
Note that the myth that any files should be marked with ''norqs'' is false. ''gendist'' automatically marks all ELF files with ''needrqs'', unless the file has been tagged with ''norqs''. Any other files, such as text files, graphics etc. will not trigger an ''rqsall'' run after installation, nor will they even be read by ''rqs''.

During most package installations using inst(1M) or swmgr(1M), certain files need to be "Re-quickstarted" using rqsall(1). When creating a new package, certain files may be marked as not needing this process using the ''norqs'' option.

== Toolchest Entries ==

== Testing and Building ==
Save the .spec and .idb files once more and move to the next worksheet. This worksheet provides the final steps in Software Packager. Click the ''Test'' button to test the package build process. It is likely that the process will complain about files missing from /usr/nekoware. Move to a shell and copy these files from /tmp/build into their respective directories in /usr/nekoware and run the test again.

It's worth it even if built with genidb to check, as genidb doesn't support post install commands or other features. 

Once the test routine passes without complaint, click the ''Build'' button and exit Software Packager. The distribution files for the package should now be in /usr/neko_dist . Change to that directory and archive these files:
 % cd /usr/neko_dist
 % tar -cf neko_fooware-1.2.3.tardist *
The next, and final, step is crucial. Change to the working directory, "-PATCHED" above, and uninstall the software:
 % su
 % gmake uninstall
 % rm /usr/nekoware/dist/neko_fooware.*
 % rm /usr/nekoware/src/fooware-1.2.3.tar.gz
 % rm /usr/nekoware/relnotes/neko_fooware.txt
 % rm /usr/nekoware/patches/neko_fooware-1.2.3_irix.patch
Now, install the package as though it were a normal Nekoware tardist:
 % inst -f /usr/dist/neko_fooware-1.2.3.tardist
Verify that the software installs correctly and runs as before, with no errors. If it installs and runs correctly, contact Raion on the forums for instructions. 

== Postprocessing ==
Certain installed files may require some kind of post-processing to integrate or register them with e.g. a service or database that is part of another package. The steps necessary will either be documented in the installation instructions or silently performed as part of ''make install''. In the latter case, one will have to carefully inspect the output and determine if any special action needs to be taken. Examples of files that require post-processing are Icons or texinfo pages. While the tools to install icons are likely already installed on the system, the ''install-info'' tool would warrant an additional prerequisite in the spec file for the subsystem containing the file. When you have determined the commands required, add an appropriate exitop to the idb file. For a texinfo file, the exitop may look as follows:
 f 0644 root sys usr/nekoware/info/foo.info usr/nekoware/info/foo.info neko_foo.man.info exitop('if test -x $rbase/usr/nekoware/bin/install-info; then chroot $rbase /sbin/sh -c "/usr/nekoware/bin/install-info --info-dir=/usr/nekoware/info /usr/nekoware/info/foo.info;" ; fi')
For Perl modules, ''perllocal.pod'' should not be installed, but amended as follows:
 f 0555 root sys usr/nekoware/lib/pidgin/perl/auto/Pidgin/Pidgin.so install/usr/nekoware/lib/pidgin/perl/auto/Pidgin/Pidgin.so neko_pidgin.sw.lib exitop('$rbase/usr/nekoware/bin/perl -MExtUtils::Command::MM -e "perllocal_install" --  "Module" "Pidgin"  "installed into" "/usr/nekoware/lib/perl5"  LINKTYPE "dynamic"  VERSION "0.01"  EXE_FILES ""  &gt;&gt; $rbase/usr/src/pidgin/install/usr/nekoware/lib/perl5/irix-n32/perllocal.pod')

== Standardization of nekoware ==
The package release notes should be installed by default. Also please put man pages in /usr/nekoware/share/man rather than /usr/nekoware/man, etc. It may be necessary to have to override some default locations (e.g. "--mandir=$PREFIX/share/man" instead of "--mandir=$PREFIX/man").

== Quality Standards ==
Updated later

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>c9b0e60838ac83f9e4ea9894b37a607c79e32582</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Tape Drives</title>
  <ns>0</ns>
  <id>142</id>
  <revision>
    <id>290</id>
    <timestamp>2025-02-23T05:24:47Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Several kinds of tape drives are supported in IRIX.  === Ultrium/LTO Drives === [[LTO Drives]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="94" xml:space="preserve">Several kinds of tape drives are supported in IRIX.

=== Ultrium/LTO Drives ===
[[LTO Drives]]</text>
    <sha1>0af996e0804494cb856c033ccacfd2511322b1cf</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>LTO Drives</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>291</id>
    <parentid>33</parentid>
    <timestamp>2025-02-23T05:25:29Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6682" xml:space="preserve">
LTO drives, also called Ultrium drives, are magnetic [[Tape Drives]] backup drives that can store larger amounts of data than [[DDS Tape]] drives can and are well-supported under IRIX.

=== Configuration ===
To configure an LTO drive requires a configuration to be placed in /var/sysgen/master.d/scsi.

=== Compatibility ===
Most documented cases include LTO1 through 4 drives. Others could potentially work but have not been tried.

=== Examples ===
&lt;pre&gt;
/* HP Ultrium 1 / LTO-1 */
{ DATTAPE, TPDAT, 2, 7, "HP", "Ultrium", /*LTO-1*/, 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_COMPRESS|MTCAN_PREV|
MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
MTCAN_SILI|MTCAN_SEEK|MTCAN_CHTYPEANY,
/* minimum delay on i/o is 4 minutes, because when a retry is
* performed, the drive retries a number of times, and then
* rewinds to BOT, repositions, and tries again. */
40, 5*60, 20*60, 20*60, 3*3600, 512, 512*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* IBM LTO-2 / Ultrium-TD2 */
{ DATTAPE, TPDAT, 3, 11, "IBM", "ULTRIUM-TD2", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* IBM LTO-3 / Ultrium-TD3 */
{ DATTAPE, TPDAT, 3, 11, "IBM", "ULTRIUM-TD3", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Quantum SuperDLT-1 */
{ DECDLT, TPDLT, 7, 9, "QUANTUM", "SuperDLT1", 0, 0, {0},
MTCAN_BSF | MTCAN_BSR | MTCAN_APPEND | MTCAN_SPEOD |
MTCAN_CHKRDY | MTCAN_VAR | MTCAN_SETSZ | MTCAN_SILI |
MTCAN_SEEK | MTCAN_SYNC | MTCAN_CHTYPEANY | MTCAN_COMPRESS,
20, 8*60, 20*60, 5*60, 3*3600, 4096, 64*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* HP LTO3 / Ultrium 3 */
{ DATTAPE, TPDAT, 2, 9, "HP", "Ultrium 3", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|MTCAN_PART|MTCAN_PREV|
MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
MTCAN_SILI|MTCAN_AUDIO|MTCAN_SEEK|MTCAN_CHTYPEANY|MTCAN_COMPRESS,
40, 5*60, 20*60, 20*60, 3*3600, 512, 512*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Certance LTO-2 / Ultrium 2 */
{ DATTAPE, TPDAT, 8, 9, "CERTANCE", "ULTRIUM 2", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },

&lt;/pre&gt;&lt;pre&gt;
/* Quantum LTO3 / Ultrium 3 */
{ DATTAPE, TPDAT, 8, 9, "CERTANCE", "ULTRIUM 3", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|MTCAN_PART|MTCAN_PREV|
MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
MTCAN_SILI|MTCAN_AUDIO|MTCAN_SEEK|MTCAN_CHTYPEANY|MTCAN_COMPRESS,
40, 5*60, 20*60, 20*60, 3*3600, 512, 512*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* HP LTO4 / Ultrium 4 */
{ DATTAPE, TPDAT, 2, 9, "HP", "Ultrium 4", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|MTCAN_PART|MTCAN_PREV|
MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|MTCAN_SETSZ|
MTCAN_SILI|MTCAN_AUDIO|MTCAN_SEEK|MTCAN_CHTYPEANY|MTCAN_COMPRESS,
40, 5*60, 20*60, 3*3600, 512, 256*512, 512*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Quantum SDLT220 drive */
{ DECDLT, TPDLT, 7, 7, "QUANTUM", "SDLT220", 0, 0,
{0}, MTCAN_BSF | MTCAN_BSR | MTCAN_APPEND | MTCAN_SPEOD |
MTCAN_CHKRDY | MTCAN_VAR | MTCAN_SETSZ | MTCAN_SILI | MTCAN_SEEK|
MTCAN_SYNC | MTCAN_CHTYPEANY | MTCAN_COMPRESS | MTCAN_SETDEN,
20, 8*60, 20*60, 5*60, 3*3600, 4096, 64*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;


/* Quantum SDLT320 drive */
{ DECDLT, TPDLT, 7, 7, "QUANTUM", "SDLT320", 0, 0,
{0}, MTCAN_BSF | MTCAN_BSR | MTCAN_APPEND | MTCAN_SPEOD |
MTCAN_CHKRDY | MTCAN_VAR | MTCAN_SETSZ | MTCAN_SILI | MTCAN_SEEK|
MTCAN_SYNC | MTCAN_CHTYPEANY | MTCAN_COMPRESS | MTCAN_SETDEN,
20, 8*60, 20*60, 5*60, 3*3600, 4096, 64*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Quantum SDLT600 drive */
{ DECDLT, TPDLT, 7, 7, "QUANTUM", "SDLT600", 0, 0, {0, 0, 0, 0 },
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SPEOD |
MTCAN_CHKRDY|MTCAN_VAR| MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|
MTCAN_SYNC|MTCAN_CHTYPEANY | MTCAN_COMPRESS | MTCAN_SETDEN,
20, 8*60, 20*60, 5*60, 3*3600, 16384, 64*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names, tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },

&lt;/pre&gt;&lt;pre&gt;
/* SONY GY-8240 DTF2 drive */
{ SONYGY, TPGY2120, 4, 7, "SONY", "GY-8240", 0, 0, {0, 0, 0, 0},
MTCAN_BSF | MTCAN_BSR | MTCANT_RET | MTCAN_CHKRDY | MTCAN_PREV |
MTCAN_SEEK | MTCAN_APPEND | MTCAN_SILI | MTCAN_VAR | MTCAN_SETSZ |
MTCAN_CHTYPEANY | MTCAN_COMPRESS,
20, 100*60, 10*60, 9*60, 9*60, 16384, 256*1024,
tpsc_default_dens_count, tpsc_default_hwg_dens_names, tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* IBM LTO-2 / Ultrium-TD2 */
{ DATTAPE, TPDAT, 3, 11, "IBM", "ULTRIUM-TD2", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;&lt;pre&gt;
/* Certance LTO-2 / Ultrium 2 */
{ DATTAPE, TPDAT, 8, 9, "CERTANCE", "ULTRIUM 2", 0, 0, {0},
MTCAN_BSF|MTCAN_BSR|MTCAN_APPEND|MTCAN_SETMK|
MTCAN_PREV|MTCAN_SYNC|MTCAN_SPEOD|MTCAN_CHKRDY|MTCAN_VAR|
MTCAN_SETSZ|MTCAN_SILI|MTCAN_SEEK|MTCAN_COMPRESS,
40, 5*60, 10*60, 10*60, 3*3600, 512, 256*512,
tpsc_default_dens_count, tpsc_default_hwg_dens_names,
tpsc_default_alias_dens_names,
{0}, 0, 0, 0,
0, (u_char *)0 },
&lt;/pre&gt;</text>
    <sha1>de0821a6c04c3e04c569164c0396592b99d28152</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>DDS Tape</title>
  <ns>0</ns>
  <id>143</id>
  <revision>
    <id>292</id>
    <timestamp>2025-02-23T05:28:17Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "'''Digital Data Storage''' ('''DDS''') is a [[Tape Drives|digital tape format]] that is based upon the '''DAT''' format that was developed during the 1980s. IRIX has supported DDS drives.    Still gathering info."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="212" xml:space="preserve">'''Digital Data Storage''' ('''DDS''') is a [[Tape Drives|digital tape format]] that is based upon the '''DAT''' format that was developed during the 1980s. IRIX has supported DDS drives. 


Still gathering info.</text>
    <sha1>b8d299746ed8e78b4ba31871284e08675b039af9</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Serial Tablets</title>
  <ns>0</ns>
  <id>144</id>
  <revision>
    <id>295</id>
    <timestamp>2025-02-23T05:30:34Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Serial tablets such as '''Wacom''' are supported in IRIX as an input device."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="76" xml:space="preserve">Serial tablets such as '''Wacom''' are supported in IRIX as an input device.</text>
    <sha1>81fa4951cd09cb5d9e598538655c12efbac5362b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>CD Installation of IRIX</title>
  <ns>0</ns>
  <id>145</id>
  <revision>
    <id>297</id>
    <timestamp>2025-02-23T07:01:43Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "IRIX can be installed via CD starting with IRIX 4.x. However, this guide specifically covers [[IRIX 6.5]]. The reason for this is that pre IRIX 6.5 installation media is often system specific, and no better way of doing it has been found other than referring to official SGI documentation and contacting people who have done it.   === Required CDs ===  * IRIX Foundation 1 * IRIX Foundation 2 * IRIX Development Libraries * IRIX Development Foundation 1.3 * IRIX Overlays (6...."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3419" xml:space="preserve">IRIX can be installed via CD starting with IRIX 4.x. However, this guide specifically covers [[IRIX 6.5]]. The reason for this is that pre IRIX 6.5 installation media is often system specific, and no better way of doing it has been found other than referring to official SGI documentation and contacting people who have done it. 

=== Required CDs ===

* IRIX Foundation 1
* IRIX Foundation 2
* IRIX Development Libraries
* IRIX Development Foundation 1.3
* IRIX Overlays (6.5.22 and up have 3 discs)
* IRIX Applications
* IRIX Mipspro Compiler Execution Environment
* IRIX Mipspro C Compiler
* IRIX MIPSPro C++ Compiler
* IRIX ONC3/NFS

This is a bare minimum for a functional install. 

=== Setting up a disklabel ===
Insert the CD after turning on the SGI and stopping at the Stop for Maintenance screen. Enter the Command Monitor. 

Type &lt;code&gt;hinv&lt;/code&gt; to get a list of SCSI devices. Look for the section labeled SCSI CDROM. The first number is the controller ID, the second the device ID. If it doesn't show up, or multiple show up, then the system has a SCSI misconfiguration. Best course of action is to receive help from the community in that situation. 

Make sure Overlay 1 is inserted. Boot sash (standalone shell):

==== 32-bit SGI ====
&lt;code&gt;boot -f dksc(0,4,8)sashARCS&lt;/code&gt;

&lt;code&gt;boot -f dksc(0,4,7)fx.ARCS --x&lt;/code&gt;

==== 64-bit SGI ====
&lt;code&gt;boot -f dksc(0,4,8)sash64&lt;/code&gt;

&lt;code&gt;boot -f dksc(0,4,7)fx.64 --x&lt;/code&gt;

==== Using fx ====
If done correctly, the output should look like:&lt;pre&gt;
fx version 6.5, Oct  1, 1999
fx: "device-name" = (dksc)
fx: ctlr# = (0)
fx: drive# = (1)
fx: lun# = (0)
...opening dksc(0,1,0)

fx: partitions in use detected on device
fx: devname             seq owner   state
fx: /dev/rdsk/dks0d1s0    1 xfs     already in use

...drive selftest...OK
Scsi drive type == SGI     IBM DDRS-34560W S96A

----- please choose one (? for help, .. to quit this menu)-----
[exi]t             [d]ebug/           [l]abel/           [a]uto
[b]adblock/        [exe]rcise/        [r]epartition/
&lt;/pre&gt;Or otherwise at a prompt. It may require hitting enter a few times or if the system has multiple discs, selecting the proper IDs. 

Type:

&lt;code&gt;repartition&lt;/code&gt;

&lt;code&gt;ro&lt;/code&gt;

&lt;code&gt;../label&lt;/code&gt;

&lt;code&gt;sync&lt;/code&gt;

&lt;code&gt;/exit&lt;/code&gt;

and it should reboot or drop back into PROM. 

=== Install via CD ===
Select Install System Software from the ARCS screen and select CD, follow the instructions. 

After getting in, it should drop into an inst&gt; prompt. Select admin, then mkfs. For a 4G or smaller drive, select 512-byte. For larger, do 4096-byte. 

Next, open each CD in inst. Hit open, then /CDROM/dist. Do this for each CD, swapping them through. 

To setup the install:&lt;pre&gt;
keep *

install standard

keep appletalk kerberos openssl openssh OpenOffice outbox sgi_apache ftn* gsview ghostscript sgitcl_eoe

&lt;/pre&gt;These components are often replaced by FOSS versions under IRIX. 

Then, get ready to swap CDs. Really nothing else to say here. Get ready to stick around for 1-2 hours going CD to CD.

== Reasons to NOT install via CD ==
IRIX CDs are expensive collectors items. IRIX CDs are EFS images and difficult to burn on IRIX. The CD swapping aspect is bad. Anyone with basic UNIX knowledge and networking (and a BSD, Solaris, IRIX or even GNU/Linux box) can do this install faster and easier using any other method. 
[[Category: Tutorials]]
[[Category: No-Images]]</text>
    <sha1>0a15cadb23efe9e942a3fa2a518da5e647e2c7b5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Tezro</title>
  <ns>0</ns>
  <id>55</id>
  <revision>
    <id>300</id>
    <parentid>188</parentid>
    <timestamp>2025-02-23T17:38:43Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3461" xml:space="preserve">For the rackmount variant of the SGI Onyx 350 branded as a Tezro, see [[Origin 350]].
[[File:Tezro-frontal.jpg|thumb|SGI Tezro, Front-profile view]]

The Silicon Graphics Tezro (styled as silicon graphics tezro) is a high-end workstation introduced by Silicon Graphics in July 2003 to replace the [[Octane]]. Built on the Chimera architecture, the Tezro is closely related to the Origin 350 and Onyx 350 systems offered by SGI during the same time period and shares the graphics module, node boards, drive sleds and some cooling parts. The Tezro is essentially a single-node Onyx 350 mounted on its side and connected like a sandwich to the IO backplane. The system was succeeded late in 2006 to early 2007 with the launch of the Prism. The Onyx4 launched alongside it, though that utilized the ATi developed UltimateVision. This distinction makes the Tezro the last machine designed by SGI to use an in-house graphics architecture. The Tezro is highly sought after in the collector market for its style, power, and for the distinction of being SGI's last MIPS workstation.

== Features ==
The Tezro is powered by the MIPS R16000 series of processors and came in dual and quad CPU node boards. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|4MB
|700,800
|700,800
|-
|8MB
|700,800
|700,800
|-
|16MB
|1000MHz
|1000MHz
|}
The Tezro can take anywhere from 512M to 8G of DDR RAM, using the same proprietary DIMMs as the Fuel, Origin/Onyx 300,350, and 3000 series.

A maximum of two 300GB U160 SCSI drives can be added to the system via the front access panel using the Origin/Onyx 350-style sleds.

Tezro supports the V10 and V12 graphics options. Dual-channel options were produced, allowing up to two 1920x1200 displays. The V12 was the only **shipped** configuration, but some machines were field replaced with V10s, or have been replaced by end users to re-purpose V12s for other machines.

The IO9 card provides SCSI backplane support, 3.5mm Audio, and a 100Mbit Ethernet port. Six PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more. A DMedia card can be added to provide DMedia support as well.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== Hardware Problems ===
The fans are controlled by environmental monitoring and the system will refuse to boot if the fans do not all respond.

The 1GHz/1000MHz CPU boards are known to overheat quickly due to inadequate airflow in the case. It's advisable to set external temperature monitoring and alarms and to not run the machine unattended, as this risks VRM or CPU failure. The latter means a new node board.

=== Form Factor and Transportation ===
The Tezro measures 21 x 14 x 17 inches in L x W x H dimensions and weighs at minimum 61lbs, more if it is heavily equipped. The front access panel is very fragile, and the system should not be held by the plastics as they grow brittle with age.

The unit has wheels on the rear, allowing for easy movement on hard surfaces. It should be carried gently and preferably with the rear of the unit supporting the weight, not the sides or the front.

=== Operating System Support ===
The Tezro was supported beginning with IRIX 6.5.15, through the final 6.5.30 release.

[[Category:Hardware]]</text>
    <sha1>429ebaa97760df6237fa00181f1a7cccd2edd9cb</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-20 18:24:57+00|253">
  <title>Onyx</title>
  <ns>0</ns>
  <id>53</id>
  <revision>
    <id>302</id>
    <parentid>181</parentid>
    <timestamp>2025-02-23T17:40:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="45605" xml:space="preserve">[[File:Onyx2 with Multichannel.jpg|thumb|Multichannel Display option for an Onyx]]
The Silicon Graphics Onyx (frequently known as the Onyx1 or Original Onyx, or by its form-factor specific codenames Eveready and Terminator) is a graphics supercomputer introduced by Silicon Graphics in 1993 to replace their short-lived [[Crimson]]. Also based on the POWERpath-2 Everest architecture, the Onyx is closely related to the Challenge L/XL systems offered by SGI during the same time period, and shares many parts. In general, the difference between an Onyx and a Challenge L/XL is that while the Challenge usually supports more CPUs and memory (with the exception of the Challenge DM), it does not support the installation of a graphics boardset (with the exception of the Challenge GR). The Onyx sat at the high-end of SGI's early-to-mid 1990s product line, above both the Indigo2 and Indy, and was used for tasks such as visualization, simulation, and early virtual reality systems. The system was succeeded on October 7th, 1996 with the launch of the [[Onyx2]]. Though production of new Onyxes ended in March of 1999, with the end of service in December of 2008, SGI continued to use the Onyx brand name on their most capable graphics systems until July of 2003, with the introduction of the Onyx4. 

== Variants and Naming ==
The Onyx is a highly modular system, and was offered in a number of processor and graphics combinations throughout its lifespan. Though some configurations (such as an R8000-based Onyx with VTX graphics) were not offered officially, most CPU/Graphics combinations were, each under a different name. There were ten different, individually named "major variants" of the Onyx. The table below describes these.
{| class="wikitable"
| colspan="6" |Table of officially-offered Onyx Variants
|-
|Variant Name
| colspan="5" |Meaning
|-
|Onyx RealityEngine2
| colspan="5" |An R4000-based Onyx using a RealityEngine2 graphics subsystem
|-
|Onyx VTX
| colspan="5" |An R4000-based Onyx using a VTX graphics subsystem
|-
|Onyx Extreme
| colspan="5" |An R4000-based Onyx using an Extreme Graphics graphics subsystem
|-
|POWER Onyx RealityEngine2
| colspan="5" |An R8000-based Onyx using a RealityEngine2 graphics subsystem
|-
|POWER Onyx Extreme
| colspan="5" |An R8000-based Onyx using an Extreme Graphics graphics subsystem
|-
|Onyx InfiniteReality
| colspan="5" |An R4000-based Onyx using an InfiniteReality graphics subsystem
|-
|Onyx 10000 RealityEngine2
| colspan="5" |An R10000-based Onyx using a RealityEngine2 graphics subsystem
|-
|Onyx 10000 InfiniteReality
| colspan="5" |An R10000-based Onyx using an InfiniteReality graphics subsystem
|-
|Reality Station
| colspan="5" |An R4000 or R10000-based Onyx using a RealityEngine2 graphics subsystem. Limited to only one CPU
|-
|i-Station
| colspan="5" |An R4000 or R10000-based Onyx using an InfiniteReality graphics subsystem. Limited to only one CPU
|-
| colspan="6" |Note: SGI does not appear to have officially offered a POWER Onyx VTX, an Onyx 10000 VTX, or an Onyx 10000 Extreme.
|}
SGI Workstation/Client Periodic Table November 4th, 1994 demonstrates the naming discrepancy between Onyx and POWER Onyx systems with Extreme Graphics installed. While POWER Onyxes are labeled with a slash as POWER Onyx/Extreme, Onyxes are labeled without the slash.
[[File:Onyx-R10k.jpg|left|thumb|R10000 Onyx variant]]
In some cases, such as on their Periodic Tables, SGI also listed the number of processors after the first portion (the one which represents the CPU) of the name. For example, a system with RealityEngine2 graphics and four R4000 CPUs would be an Onyx/4 RealityEngine2, a system with RealityEngine2 graphics and twelve R8000 CPUs is a POWER Onyx/12 RealityEngine2 and so-on. Interestingly, R4000 systems with Extreme graphics do not use the "slash-CPU" notation, meaning that, for example, an system with two R4000s and a system with four R4000s, each with Extreme Graphics, are both known simply as the Onyx Extreme. The same goes for the R8000-based POWER Onyx, except that the slash is kept with only the number removed. All R8000-based Onyxes using Extreme Graphics are known simply as the POWER Onyx/Extreme. This strange phenomenon can be seen on the November 4th, 1994 Workstation/Client Periodic Table (image on right) and the very similar Workstation/Client Periodic Table rev. 2/14/95 (the only difference of which is a change to the aesthetic of the title and the removal of the Crimson RealityEngine and its replacement with the Reality Station, which is, redundantly, known there as the Reality Station RealityEngine2). While this discrepancy between the POWER Onyx and the regular, R4000 Onyx's naming schemes could be mistaken for a typo, its presence on two similar but different revisions of the Periodic Table makes this unlikely.

== Architecture ==
[[File:940110-Periodic Table.jpg|thumb|SGI Periodic Table]]
The architecture of the SGI Onyx can be roughly divided into two main parts — the POWERpath-2 bus (frequently known as EBus) and the HIO bus (also known as IBus), including the buses and interfaces which interface with the system via it. While the POWERpath-2 bus provides a high-speed interconnect for CPUs, memory, and the I/O subsystem, the HIO bus provides both direct expansion capabilities using the HIO connectors on the IO4, and interfaces to a number of other system components over FCI (via the F Controller ASICs), VMEbus (via the FCI-connected VMECC), SCSI (via the S1IC) and numerous miscellaneous interfaces (via the EPC).
[[File:Onyx RE2.png|left|thumb|Onyx2 RealityEngine2 diagram]]
POWERpath-2 is the successor to SGI's POWERpath architecture, which they had previously used in their PowerSeries and Crimson systems. While it is officially known as POWERpath-2, it is often called EBus, short for "Everest Bus", Everest being the codename for the system architecture shared by the Onyx and Challenge L/XL. While not the "true" name of the bus, the "EBus" moniker is frequently used both by Onyx owners and by SGI themselves (such as on the slot number label affixed below the slots of the Onyx cardcage). The 256-bit POWERpath-2 bus has a data transfer rate of 1.2GB/s (as compared to the 64MB/s of the original POWERpath), and is used exclusively for the system's core components, the IP19/21/25, MC3, and IO4 boards (not for add-on options or graphics boards). POWERpath-2 is unique to Everest systems (Onyx and Challenge L/XL), and was replaced with the S2MP architecture in the later Onyx2 and Origin2000.
[[File:Onyx Infinite Reality Diagram.png|thumb|InfiniteReality Onyx Diagram]]
While core components are connected to POWERpath-2, their interface with the rest of the system is provided by the IO4 board. The IO4 uses an internal 64-bit bus, which, like POWERpath-2, has two names, those being HIO and IBus. When referring to add-on cards connected to the IO4 using it, it is usually referred to as the HIO (high-speed I/O) bus. However, it is also used internally on the IO4, and it seems that the term "IBus" is preferred here. IBus has a bandwidth of 320MB/s, and is shared by HIO add-ons, VME devices and the graphics subsystem (via F Controller ASICs and the VCAM), and the IO4's built-in EPC I/O controller (which, in turn, creates another bus used for basic I/O devices, the 16-bit PBus) and S1IC SCSI controller. VME devices and graphics boards do not connect directly to IBus. Instead, the IO4 also contains two F Controller ASICs, each of which connects to IBus and creates an FCI, or Flat Cable Interface. These two FCI interfaces are exposed on two connectors towards the rear of the IO4. Attached to these connectors (resting on standoffs above the IO4's PCB, much like the HIO options in front of it) is another board known as the VCAM, or VME Channel Adapter Module. The VCAM serves two primary functions, each using one of the FCI interfaces created on the IO4.

As the name of the device states, one of these functions is to act as an adapter between the system and its VME add-on boards. VMEbus is an industry-standard bus developed by Motorola for systems based on their 68000 processor, and used in many systems both with and without the 68000. Though the Everest family were the final SGI systems to use VMEbus, it was far from the first, with many previous SGI systems and add-ons also using it. The Onyx implements VME Revision C, as well as the A64 and D64 modes of Revision D, allowing VME bandwidth up to 60MB/s when DMA is used. The deskside Onyx has 4 VME slots, one of which is filled by the VCAM, while the rack has either four or twelve slots, depending on cardcage configuration (see below for details). The VCAM provides this VME interface using its onboard VMEBus controller chip, and interfaces the VME bus to one of its FCI interfaces using the VMECC (VME Cache Controller).

The other FCI interface provided to the VCAM is simply passed through to the backplane, for use by the graphics subsystem. This is the other primary function of the VCAM. The graphics subsystem communicates with the host system over its FCI interface using its GFXCC (meaning unknown, but probably "Graphics Cache Controller", in the vein of "VME Cache Controller").

In an Onyx Rack, the number of VME slots available depends on whether the system's third cardcage is used. When only two cardcages are used, the rack Onyx has four VME slots, all in Cardcage 2, one of which is filled by the VCAM attached to the IO4. This is the same configuration found in deskside systems. When the third cardcage is used, eight more VME slots, for a total of twelve, are made available. These slots are divided into two groups, found in slots 1, 2, 3, 4 and 12, 13, 14, 15 in Cardcage 3. Slots 1 and 12, the first of each group, contain a VCAM-like board known as an RVCAM, or Remote VCAM, which provides a VME bus to the three slots next to it. No RVCAMs are required if only two cardcages are used, as the VCAM connected to the system's IO4 is sufficient to control the VME slots in Cardcage 2.

In systems equipped with Extreme Graphics, the VCAM is replaced with a GCAM (meaning unknown, but likely "GIO Channel Adapter Module", in the vein of "VME Channel Adapter Module"), effectively replacing the system's VME bus with a GIO64 bus (albeit in a strange form factor). While the exact components of the GCAM are unknown, it likely uses an ASIC in order to interface the GIO bus to one of the FCI interfaces usually used by the VCAM. Assuming the naming scheme for FCI-connected devices was followed, this chip was likely known as the GIOCC. An adapter is then used to install an Indigo2 Extreme Graphics option in a "VME" (the actual protocol is GIO, but the same physical slots on the backplane are used) slot. While both the GCAM and the adapter are relatively unknown and extremely rare, the adapter is especially hard to find details about. It has been mentioned only a few times on Nekochan Forums, with user "whiter" referring to it as "the GIO2VME adapter" in one post and "AB5 (GIO64 to 9u VME shoehorn)" in another, and user "thegoldbug" referring to it as "a small circuit board (SLAG2) with resistors that connects to the VME bus", going on to conclude that "The GCAM must be doing all the work". In a thread about this board created by whiter, another user, "kshuff", says that he owns an Onyx with Extreme Graphics, and that it was factory-installed in his system. The board appears to have been named the AB5 (possible meaning Adapter Board 5), though the names GIO2VME and SLAG2 are also possibilities, and is seemingly smaller than a usual VME-like board, while consisting of "resistors". Based on this, it is likely a small board, the electronics of which consist solely of passives, located at the rear of a VME slot and containing a GIO64 connector of the sort seen in the Indigo2. In order to mount the non-VME-sized Extreme Graphics boardset in the Onyx cardcage, as well as to affix it to the adapter board, some form of carrier, likely a simple metal frame, was probably used. How the Extreme Graphics boardset's ports were moved to the expansion panels in the cardcage door or the graphics bulkhead below is unknown. It has been noted that a spare GCAM and AB5 board could be used with an Extreme Graphics boardset from an Indigo2 in order to add graphics capabilities to a Challenge L/XL, however thegoldbug, one of the owners of this hardware mentioned above, claims to have attempted this configuration twice, using two different AB5 boards, unsuccessfully. The possibility of adding a non-Extreme GIO64 board such as an IMPACT graphics boardset or other Indigo2 card to an Everest system using the GCAM and AB5 has also been raised, however the conclusion seems to be that it would not be possible due to driver problems.

==== CPU ====
The Onyx's CPUs reside on the IP board, which is installed in a POWERpath-2 slot. Though there are 22 different CPU boards available for the Onyx, they are divided into three main categories by their IP number. While most SGI systems spanning multiple processor families use only one IP number (such as the O2, which is an IP32 system regardless of whether an R10000 or R5000 is installed), the IP number of the Onyx and its CPU board(s) is determined by its CPU family. The IP19 board contains one, two, or four R4400 (R4000-family) processors, and was originally the only processor board offered in Onyx systems. With the introduction of the POWER Onyx and the R8000, the IP21 board, containing either one or two R8000s, was released. Note that because there is no IP21 board with four processors, the usual maximum processor count of 4 in desksides and 24 in racks is halved to 2 and 12, respectively. Finally, with the introduction of the Onyx 10000, the R10000-based IP25 board was introduced, which, like the IP19 board, can contain one, two, or four processors.

Desksides allow one IP CPU board, which must be installed in its designated slot (labeled on the sticker below the cardcage). Given the maximum of four CPUs per board, this means the maximum number of CPUs that can be installed in a deskside system is four. Rack systems are significantly more flexible, having eleven EBus slots, five in Cardcage 1 and six in Cardcage 2. Slot 6 in Cardcage 2 must be filled by the master IO4 board, however the ten remaining slots can be used for either IP CPU boards or MC3 memory boards. Additionally, the five remaining EBus slots in Cardcage 2 (those not filled by the mandatory Master IO4 in Slot 6) may be used for additional IO4 boards, though the five slots in Cardcage 1 cannot. Up to six of these slots may be filled with IP boards, allowing up to 24 CPUs in an Onyx rack system.
{| class="wikitable"
| colspan="7" |Table of Onyx IP CPU Boards
|-
|SGI Part No.
|IP No.
|CPUs
|CPU
|Clock
| colspan="2" |Secondary Cache
|-
| colspan="7" |IP19 (R4000):
|-
|030-0642-xxx
|IP19
|1
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0249-00x
|IP19
|2
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0250-0xx
|IP19
|4
|R4400
|100MHz
| colspan="2" |1MB
|-
|030-0525-00x
|IP19
|1
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0374-00x
|IP19
|2
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0375-00x
|IP19
|4
|R4400
|150MHz
| colspan="2" |1MB
|-
|030-0720-00x
|IP19
|1
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0652-00x
|IP19
|2
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0653-00x
|IP19
|4
|R4400
|200MHz
| colspan="2" |4MB
|-
|030-0806-00x
|IP19
|1
|R4400
|250MHz
| colspan="2" |1MB
|-
|030-0805-00x
|IP19
|2
|R4400
|250MHz
| colspan="2" |4MB
|-
|030-0804-00x
|IP19
|4
|R4400
|250MHz
| colspan="2" |4MB
|-
| colspan="7" |IP21 (R8000):
|-
|030-0636-00x
|IP21
|1
|R8000
|75MHz
| colspan="2" |4MB
|-
|030-0625-00x
|IP21
|2
|R8000
|75MHz
| colspan="2" |4MB
|-
|030-0751-00x
|IP21
|1
|R8000
|90MHz
| colspan="2" |4MB
|-
|030-0702-00x
|IP21
|2
|R8000
|90MHz
| colspan="2" |4MB
|-
| colspan="7" |IP25 (R10000):
|-
|013-1672-00x
|IP25
|1
|R10000
|195MHz
| colspan="2" |1MB
|-
|013-1675-00x
|IP25
|1
|R10000
|195MHz
| colspan="2" |2MB
|-
|030-1107-xxx
|IP25
|2
|R10000
|195MHz
| colspan="2" |1MB or 2MB
|-
|030-1107-xxx
|IP25
|4
|R10000
|195MHz
| colspan="2" |1MB or 2MB
|-
|030-1673-00x
|IP25
|4
|R10000
|195MHz
| colspan="2" |2MB
|-
|030-1673-101
|IP25
|4
|R10000
|195MHz
| colspan="2" |2MB
|-
| colspan="7" |Note: The 030-1673-101 board is unable to load IRIX 6.2, due to its use of CPU Version 3.1. 6.5.x must be used.
|}
The secondary cache of the IP19 board is installed on SIMM modules, though these are not the same ones found in the MC3's slots. These are available in capacities of 256KB and 1MB. The 1MB SIMM is not only four times larger in terms of capacity, but also has a slightly reduced latency.
{| class="wikitable"
| colspan="7" |Table of Onyx IP19 secondary cache SIMMs
|-
|SGI Part No.
|Capacity
|Latency
| colspan="4" |Color Code
|-
|030-0324-00x
|256KB
|10ns
| colspan="4" |Blue Stripe
|-
|030-0660-00x
|1MB
|8ns
| colspan="4" |Yellow Stripe
|}

==== Memory ====
Memory is installed in the Onyx using one or more MC3 boards. A deskside system can take one MC3 board, while a rack can take up to 8. Note that this means that it is impossible for an Onyx rack to have both the maximum CPU configuration and the maximum RAM configuration, as there are simply not enough EBus slots for 8 MC3s and 6 IP boards, let alone any IO4 boards. The MC3 board has 32 slots, each of which can accept a single SIMM of special ECC-protected memory. Three different models of memory SIMM exist, in capacities of 16 and 64 megabytes (with the 64MB version existing in two different variants). The following is a list of MC3 board revisions. It is believed that all revisions should be interchangeable with no effect on compatibility with other parts. However, this has not been exhaustively tested, and as such it is recommended to leave a working system's MC3 board in place when possible, as all MC3 revisions are essentially equivalent in functionality.

List of Onyx MC3 Memory Board Revisions (by SGI Part Number)030-0245-00x

* 030-0604-xxx
* 030-0607-001
* 030-0613-xxx
* 030-0614-xxx
* 030-0614-106

The following is a table of available Onyx memory SIMMs, to be installed on the MC3.
{| class="wikitable"
| colspan="7" |Table of Onyx MC3 Memory SIMMs
|-
|SGI Part No.
|Capacity
|Latency
|Color Code
| colspan="3" |Construction
|-
| colspan="7" |16MB:
|-
|030-0256-00x
|16MB
|60ns
|Pink Stripe
| colspan="3" |Single PCB
|-
| colspan="7" |64MB:
|-
|030-0257-001
|64MB
|60ns
|Purple Stripe
| colspan="3" |Dual-PCB ("Sandwich")
|-
|030-0257-002
|64MB
|60ns
|Purple Stripe
| colspan="3" |Single PCB
|}

==== Graphics ====
Throughout its lifespan, the Onyx was available with four different graphics options. Initially released with a choice of RealityEngine2 or VTX, options for Extreme graphics and InfiniteReality were introduced later.

The performance characteristics of these graphics options are provided in the table below, for easy comparison.
{| class="wikitable"
| colspan="7" |Performance Characteristics and Features of Onyx Graphics Options
|-
|
|RealityEngine2
|VTX
|InfiniteReality
| colspan="3" |Extreme
|-
|Anti-aliased vectors/sec
|2.0M
|1.0M
|7.4M
| colspan="3" |?
|-
|Triangle Meshes/sec
|1.6M
|1.1M
|11M
| colspan="3" |?
|-
|T-Mesh Gouraud Z, lit
|1.0M
|813K
|?
| colspan="3" |?
|-
|T-Mesh Textured
|988K
|600K
|?
| colspan="3" |?
|-
|Quad Strips, Gouraud, Z
|988K
|600K
|?
| colspan="3" |?
|-
|Pixel Fill, smooth, Z
|90M (1x RM )
180M (2x RM)
360M (4x RM)
|90M
|224M (1x RM)
~450M (2x RM)
"&gt;800M" (4x RM)
| colspan="3" |?
|-
|Pixel Fill, Textured, AA
|55M (1x RM)
~115M (2x RM)
230M (4x RM)
|Presumably 55M
|194M (1x RM)
~400M (2x RM)
"&gt;750M" (4x RM)
| colspan="3" |?
|-
|Trilinear Interpolations/sec
|40M (1x RM)
80M (2x RM)
160M (4x RM)
|Presumably 40M
|"&gt;200M" (1x RM)
~400M (2x RM)
"&gt;800M" (4x RM)
| colspan="3" |?
|-
|Convolutions 5x5 separable
|20M
|?
|? (SGI says "TBD")
| colspan="3" |?
|-
|Z-Buffer
|32-bit Integer
|32-bit Integer (?)
|24-bit Floating Point
| colspan="3" |?
|-
|Color
|48-bit RGBA
|48-bit RGB
|48-bit RGBA
| colspan="3" |?
|-
|Color Planes
|192
|192
|192
| colspan="3" |?
|-
|Overlay Planes*
|8
|8
|16
| colspan="3" |?
|-
|Underlay Planes*
|8
|8
|None (?)
| colspan="3" |?
|-
|Max Bits-per-pixel
|256 (1x RM)
512 (2x RM)
1024 (4x RM)
|256
|256 (1x RM)
|512(?) (2x RM)
|1024 (4x RM)
|?
|-
|Texture Memory
|4MB (RM4)
16MB (RM5)
|4MB (RM4)
16MB (RM5)
|16MB (RM6-16)
64MB (RM6-64)
| colspan="3" |?
|-
|Framebuffer Size
|40MB (1x RM)
80MB (2x RM)
160MB (4x RM)
|40MB
|80MB (1x RM)
160MB (2x RM)
320MB (4x RM)
| colspan="3" |?
|-
|Display
|VGA to non-interlaced HDTV (32-bit) or 1600x1200 (48-bit)
|VGA to 1280x1024
|VGA to non-interlaced HDTV
| colspan="3" |?
|-
|32-pixel Read (/sec? meaning unclear.)
|28.3M
|21.1M
|?
| colspan="3" |?
|-
|32-pixel Write (/sec? meaning unclear.)
|29.1M
|26.8M
|?
| colspan="3" |?
|}
Note: Overlay and underlay plane specifications are confusingly worded in sources, and should be taken with

a grain of salt. Meaning of "32-pixel" measurements is unknown, and they are provided verbatim, as listed in

the original source (sgistuff.net). Numbers for dual-RM setups may be interpolated from listed single and quad

specifications, marked with ~ when 4-RM measurement is not precisely 4x the 1-RM measurement. BPP of 512

in dual-RM IR setup interpolated from single being 256 and quad being 1024, however an SGI brochure lists

the dual-RM i-Station as 1024. This is believed to be an error. This brochure also lists some InfiniteReality details

as "greater than" a certain measurement (presumably a conservative estimate). This "&gt;SOMETHING" format is

preserved here. Details for Extreme Graphics are unknown at this time, and should be determined and added.

VTX specs marked "Presumably" are taken from an IR/RE2 comparison with no mention of VTX, and are based

on the single-RM RE2 figure (as VTX is architecturally identical, but has only one RM).

==== A Note on "RM" ====
The RealityEngine2, VTX, and InfiniteReality graphics options for the Onyx all utilize a board called the RMx, x being a version. In the case of the RealityEngine2 and VTX, this can be either the RM4 or RM5, whereas InfiniteReality uses one of two variants of the RM6 (RM6-16 or RM6-64). While, in most discussions, this board is referred to simply as the "RM", the meaning of the acronym is less clear than one might imagine. It appears that the majority of Onyx owners, as well as, in many cases, SGI themselves (see their website, circa 1994), refer to the board as the "Raster Manager". However, in the technical papers for both the RealityEngine2 and the InfiniteReality, the authors refer to it as the "Raster Memory" board. Because of this, it appears that, within SGI, there was either disagreement or confusion as to what "RM" stood for. While both would make for the "RM" acronym, it is generally accepted that "Raster Manager" makes more sense (as, while the board does contain memory, it also performs a significant amount of processing, rather than simply storing data).

RealityEngine2, often known as "RE2", was, at the time of its release, the highest end graphics option for the Onyx. While it was later repurposed as a lower-end counterpart to the new InfiniteReality, it was originally the most powerful option available. The RealityEngine2 is an improved version of the RealityEngine graphics offered in Crimson and PowerSeries systems, the differentiating factor being the replacement of the eight processor GE8 with the twelve processor GE10. Additionally, the need to terminate Raster Manager boards using a special "terminated" RM4T board (an RM4 with resistors installed in a socket on the board) was removed, with termination now being handled by the system's backplane. The RealityEngine2 consists of three types of board, installed in specialized graphics slots on the backplane.
{| class="wikitable"
| colspan="7" |Table of RealityEngine2 Boards
|-
|SGI Part No.
|Board Name
|Connected to Edge Connector?
|Function
| colspan="3" |Notes
|-
|030-0325-00x
|GE10
|No
|Geometry Engine - Perform geometric graphics calculations
| colspan="3" |N/A
|-
|030-0513-00x
|DG2
|Yes
|Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0359-001 RM4
|Yes
|Raster Manager - Generate image data from geometry
| colspan="4" |40MB framebuffer RAM per RM4, 4MB texture RAM regardless of board count.
|-
|030-0360-001
|RM4T
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |Like RM4, but terminated for pre-Onyx systems. Resistors in jumper block must be removed if installed in Onyx.
|-
|030-0347-00x
|RM5
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |40MB framebuffer RAM per RM5, 16MB texture RAM regardless of board count.
|-
|030-0506-00x
|PAB1
|No
|Paddleboard Interface - Connect RealityEngine2 to Sirius Video board
| colspan="3" |Connects to DG2. Not needed if Sirius Video is not installed.
|}
The GE10 board contains 12 Geometry Engines, at the center of each is an Intel I860XP (not to be confused with the similar but mostly unrelated terms "i386", "x86", "i586", and so-on) RISC processor. While the i860 family of processors never saw use as widespread as hoped, they were found in numerous other niche uses at the time, such as the NeXTcube's NeXTdimension color graphics board, as well as computers from Oki, Stardent, Hauppauge, and Olivetti. It also saw use in Intel's iPSC/860 and Paragon series supercomputers. In the RealityEngine2, these i860XP processors are used to perform geometry calculations for graphics. Each one of these chips has a combined ALU plus floating point performance of 100 megaflops, meaning that, multiplied by the Geometry Engines on the board, each containing one processor, the total compute performance of the GE10 board is 1.2 gigaflops. Each i860XP processor is provided with two megabytes of DRAM. The GE10 also houses the command processor, which is used to control the graphics subsystem and to implement the OpenGL graphics language. The output of these twelve individual geometry engines is transmitted on the Triangle Bus, for use by the RM board. Interestingly, the design of the Triangle Bus on the RealityEngine2's GE10 board is identical to that of said Triangle Bus on the original RealityEngine's GE8 board. While the increased load of the GE10's four extra geometry engines does increase utilization of Triangle Bus bandwidth, the bus was designed to support more than twice the bandwidth required by the original RealityEngine, meaning that in theory, it would work even with 16 Geometry Engines. This meant that the Triangle Bus did not need to upgraded or redesigned during the development of the GE10. The GE10 board does not connect to the edge connector board, and as such installation of a GE10 only requires that the board be inserted into the backplane, like a regular EBus or VME board.

The RM board inputs geometry data from the Triangle Bus, and outputs digital video data to the DG2. The RM board consists of two main types of processor, the Fragment Generator and the Image Engine. Each Raster Manager board consists of five Fragment Generators, with each Fragment Generator driving sixteen Image Engines. While the functionality of the Raster Manager is complex and spans many different tasks (as discussed in the "RealityEngine Graphics" paper, linked below), the basic architecture of the board inputs data from the GE10's triangle bus, before distributing it between five Fragment Generators. The Fragment Generator consists of four ASICs and eight 16 megabit (2 megabyte) DRAM chips, for a total of 16 megabytes per Fragment Generator and 80 megabytes per RM board. The output of the Fragment Generator is then fed into the input of the Image Engine. The RM4 board contains 20 IMP7 Image Engine chips, each of which contains four individual Image Engines. Each one of these IMP7 chips is surrounded by four four megabit (512 kilobyte) DRAM chips, one for each Image Engine inside. The output of these 80 Image Engines is then output to the DG2 board, by way of the edge connector board, which must be installed. The RM4 board provides 40MB of framebuffer memory per board, and adding more RM4 boards can increase this to a total of 160MB (in a four board setup). The RM4 also provides 4MB of texture RAM, though this capacity is not increased by the addition of further RM4 boards. The closely related RM4T is simply an RM4 with some resistors installed in a jumper block towards the rear of the board, for use as a terminated RM4 in a Crimson or PowerSeries system. If installing an RM4T board in an Onyx, these resistors should be removed from the jumper block prior to use, as the Onyx does not require Raster Manager termination. The newer RM5 maintains the same 40MB of framebuffer RAM, but increases texture RAM to 16MB, again not increased when additional boards are installed.

The DG and RM boards must be connected using an edge connector board, installed at the front of the cardcage and connecting all boards below it. The part number of this edge connector is 030-0233-001. This board carries 160 serial, one-bit 50mhz data paths, which together carry the output of the Image Engines to the DG2. In a single-RM system, half of these paths are used, one for each of the 80 Image Engines. In a dual-RM setup, each data path is assigned to a single Image Engine, with all 160 used. In a quad-RM system, these data paths are multiplexed, with each path carrying the output of two Image Engines. This multiplexing is likely the primary reason why a triple-RM system is not possible, as it would require a strange configuration, such as a half-multiplexed, half-direct use of all 160 paths, or some other special-case implementation. With all 160 paths in use, this board provides a bandwidth of 500 megabytes per second.

On the receiving end of the output of the Image Engines is the DG2 board. This board generates the video outputs exposed on the graphics bulkhead's connectors. The data from the Image Engines is first reassembled into what is effectively a digital video signal by ten crossbar ASICs on the DG2, before the image is dithered from 12- to 8-bit color and passed through Digital-to-Analog converters (DACs) for output to the monitor. Like the RM boards, the DG2 board must be connected to the edge connector board. The DG2 board has connectors for the Graphics Bulkhead, which is installed lower in the chassis and connects to it via ribbon cables.

==== VTX ====
VTX is a cost-reduced variant of the flagship RealityEngine2 graphics. Architecturally, a VTX subsystem is identical to a RealityEngine2, however it contains half the Geometry Engines and is limited to a single Raster Manager board. While the single RM board and the DG board are identical to those used in a RealityEngine2, VTX replaces the twelve-GE GE10 board with the six-GE GE10V. An SGI Periodic Table from 1993 lists many variants of Onyx in otherwise-identical VTX and RealityEngine2 configurations. This conveniently allows the reader to determine the price of a VTX subsystem relative to a RealityEngine2, as in all cases, systems with VTX graphics cost $40,000 USD less than their RealityEngine2 counterparts. Despite this significant cost saving to the original buyer, it appears that today, at least with regards to systems owned by collectors and those sold on the used market, VTX-powered Onyxes are significantly less common than RealityEngine2 models, perhaps indicating that the lower cost of VTX was not worth the reduced performance to many original buyers. It appears that SGI may have responded to this apparent lack of sales later in the Onyx's life cycle, with late-era Onyx marketing materials usually omitting the option of VTX entirely (though this could also be said to be because of the introduction of the new InfiniteReality graphics subsystem, effectively rendering the once high-end RealityEngine2 the Onyx's budget graphics offering).

==== InfiniteReality ====
InfiniteReality is the later of the two flagship graphics options offered for the Onyx. Being the successor to the RealityEngine2, InfiniteReality is the most powerful graphics option available for the Onyx. Like the RealityEngine2 subsystem before it, InfiniteReality consists of three types of board, the GE, DG, and RM. The primary goal of InfiniteReality was to deliver graphics of a quality similar to that of RealityEngine2 at an increased frame rate. A key goal during the development of InfiniteReality's architecture was that it would not only be fully compatible with the Onyx (in addition to the later, higher-bandwidth Onyx2), but that it would be able to utilize most of its performance on both systems. This affected many elements of the boardset's design, from its physical partitioning into GE, RM, and DG boards (so as to fit into the graphics slots in an Onyx), to its use of a display list subsystem with significant architectural changes to that used in the RealityEngine2 (see linked InfiniteReality: A Real-Time Graphics System paper). These architectural changes were necessary to adequately utilize the InfiniteReality in the Onyx, which interfaced with its graphics at a data rate of approximately 200MB/s, in addition to the roughly twice-as-fast Onyx2, which managed 400MB/s.

Like the RealityEngine2, the InfiniteReality uses one GE board, one DG board, and one, two, or four RM boards, connected to the DG via frontplane card-edge connector board. It should be noted that InfiniteReality's RM boards have a greater power consumption than those used in the RealityEngine2, and, as such, only one or two can officially be used in a deskside (while four is limited to a rack). Despite this limitation, it is rumored that, by installing the power boards from a rack system in a deskside, the system could theoretically power four RMs. While it may be possible to provide sufficient power for the additional boards in a deskside, cooling them is still likely to be difficult for the deskside's smaller fans. While a four-RM deskside would certainly be a rare (possibly even unique), powerful, and compact system, those attempting this configuration should exercise extreme caution, understand that they risk severely damaging their system (especially if it seriously overheats), and should understand that this configuration is unsupported and potentially not even possible. Those seeking a reliable, known-good 4-RM InfiniteReality system are advised to look into an Onyx or Onyx2 rack system, where four RMs is an official configuration, and the system already has the necessary cooling and power capacity without any modification.
{| class="wikitable"
| colspan="7" |Table of InfiniteReality Boards
|-
|SGI Part No.
|Board Name
|Connected to Edge Connector?
|Function
| colspan="3" |Notes
|-
|030-0681-003
|GE12-4
|No
|Geometry Engine - Perform geometric graphics calculations
| colspan="3" |"-4" meaningless on Onyx, denotes 4 GEs. Onyx2's GE14 also had a 2 GE "-2" version (in Reality Graphics systems).
|-
|030-0686-004
|DG4-2
|Yes
|Two-channel Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0687-004
|DG4-8
|Yes
|Eight-channel Display Generator - Generate video output to monitor, etc
| colspan="3" |N/A
|-
|030-0683-004
|RM6-16
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |80MB framebuffer RAM per RM6-16, 16MB texture RAM regardless of board count.
|-
|030-0684-004
|RM6-64
|Yes
|Raster Manager - Generate image data from geometry
| colspan="3" |80MB framebuffer RAM per RM6-64, 64MB texture RAM regardless of board count.
|-
|030-0506-00x
|PAB2
|No
|Paddleboard Interface - Connect InfiniteReality to Sirius Video board
| colspan="3" |Connects to DG4-2 or DG4-8. Not needed if Sirius Video is not installed.
|}
Like in the RealityEngine2, data moving through the InfiniteReality begins on the GE board. It is accessed from the host system using the Host Interface Processor, which then provides it to the Geometry Distributor. The Geometry Distributor handles distribution of geometry processing workload among the GE board's four Geometry Engines. The Geometry Distributor is capable of distributing data using either a round-robin or least-busy distribution scheme, though least-busy has a slight performance advantage. The Geometry Distributor provides data to the Geometry Engines in the form of commands, each of which contains an identifier assigned by the Geometry Distributor. The Geometry-Raster FIFO buffer later uses these identifiers to reconstruct the order of the commands before they were sent to the Geometry Engines.

Unlike RealityEngine2's twelve Intel i860 XP processors, InfiniteReality uses four custom in-house ASICs. The Geometry Engine chips used by InfiniteReality each contain three cores, meaning that, like it's predecessor's 12 i860 XPs, the InfiniteReality could be said to have twelve processors for geometry (three in each of the four ASICs). However, this analogy should be used with caution. While the RealityEngine2 truly did have 12 Geometry Engines, each three-core InfinteReality ASIC contains only one 2560-word (32-bit words) on-chip memory, shared by all three of its cores. As such, even ignoring the fact that they are no longer on separate chips, the cores that make up an InfiniteReality Geometry Engine are not as independent with regards to memory as the Geometry Engines are on the RealityEngine2 (where each i860 XP has access to 2MB of its own, off-chip DRAM). This single memory for all three cores also allows them to easily share data, if necessary.

At the output of the four Geometry Engines lies the Geometry-Raster FIFO, an SDRAM-based FIFO buffer capable of storing up to 65536 vertices. As stated above, this FIFO is also responsible for properly ordering its data, based on the identifiers assigned by Geometry Distributor.

The data then moves from the GE board to the RM boards, via the Vertex Bus. While the purpose of the Vertex Bus (to carry data between the GE and RM boards) is similar to that of the RealityEngine2's Triangle Bus, it is implemented differently (see paper linked below), resulting in a significant performance improvement. Data sent over the Vertex Bus is broadcast to all Fragment Generators. The InfiniteReality RM board contains a single Fragment Generator and 80 Image Engines. The Fragment Generator is, as was also the case with its predecessor, composed of multiple chips (the SC Scan Converter, TA Texel Address Calculator, eight TM Texture Memory controllers, and four TF Texture Filtering ASICs). Like on the RealityEngine2, data from the GE board is first processed by the Fragment Generator, then by the Image Engines. Because there is only one per RM board, an InfiniteReality RM board's single Fragment Generator uses all 80 of the image engines on the board, unlike on the RealityEngine2, where each of the five Fragment Generators is given 16 of the 80 total Image Engines. The InfiniteReality also continues the trend of combining four individual Image Engines onto a single Image Engine chip, meaning that only 20 Image Engine chips are needed.

Two variants of the Onyx InfiniteReality RM board are available. The RM6-16 has 16MB of Texture RAM (TRAM), while the RM6-64 has 64MB. Each RM board maintains one copy of texture RAM, meaning that, while the amount of physical texture memory in a system increases when additional RM boards are installed, the amount of usable texture memory remains the same, as the memory on the newly-installed RM board(s) is used simply duplicate the data on the existing RM(s). Because each board must retain its own copy of texture RAM, RM6-16 and RM6-64 boards cannot be mixed in a single system (as, having only a quarter the texture memory, an RM6-16 would be unable to store a full copy of the texture memory contents of an RM6-64). Both the RM6-16 and RM6-64 have 80MB of framebuffer RAM per RM board, double the 40MB seen on the RealityEngine2. Unlike TRAM, framebuffer RAM is not duplicated between RM boards, meaning that more RM boards will increase the total amount of framebuffer RAM in the graphics subsystem, up to a maximum of 320MB (with four RM boards).

Like on the RealityEngine2, the output of the RM boards is sent to the DG board via an edge connector board mounted at the front of the cardcage. The edge connector spans the four RMs, connecting to each, and also connects to the DG board, but does not connect to the GE board or any other boards in the cardcage. This edge connector carries 160 serial data paths, the same configuration used in the RealityEngine2, however their use is more flexible on InfiniteReality systems. The RealityEngine2 utilizes one path per Image Engine in one-RM and two-RM configurations, and multiplexes the outputs of each pair of Image Engines onto a single path in a four-RM configuration. This means that, while the video bandwidth of the frontplane is fully utilized in two-RM and four-RM setups, where all 160 paths are driven by at least one Image Engine, single-RM systems utilize only half of the bandwidth, leaving the other 80 paths unused. Though an InfinteReality system also has only 160 paths for its potential 320 Image Engines, it uses them more efficiently in single-RM configurations. While two RMs will assign one path to each of the 160 Image Engines, and four RMs will multiplex the output of 320 Image Engines onto 160 paths, single-RM InfiniteReality systems allow each of the 80 Image Engines to drive two of the 160 data paths on the frontplane, doubling per-Image-Engine bandwidth. Since InfiniteReality systems use all 160 data paths in all configurations, the bandwidth of the InfiniteReality frontplane is a fixed 1200MB/s.

These 160 signals are recieved by four ASICs at the input of the Display Generator board (these ASICs also add the cursor on top of the incoming video). The video is then sent to one of the Display Generator's two or eight (see below) channels. A DG channel is able to resize its video in realtime (e.g. for output as NTSC/PAL video), and can also control the timing of its output. This timing control is the purpose of the Genlock and Swap Ready BNC connectors on the graphics bulkhead, and is discussed in greater depth in the "InfiniteReality: A Real-Time Graphics System" paper linked below. The channel's 12-bit-per-component digital video signal is then passed through 8-bit DACs, which generate the final analog video signal. It should be noted that Channel 1 contains additional hardware, not found on other channels, allowing it to also output composite and S-Video signals.

InfiniteReality's DG4 board is available in two variants. The DG4-2 has two channels, and was the lower-end "standard" option, while the higher-end DG4-8 has eight channels. It should be noted that the DG4-2 PCB has footprints for the components required to provide extra six channels, however, these components are unpopulated. Particularly noticeable are the footprints for the six large BGA chips along the edge of the board, as well as the six QFPs beside them. Towards the middle of the board is a connector for the PAB2 Sirius Video paddleboard, which must be installed if the InfiniteReality boardset is being used alongside a Sirius Video board. The DG4 board has connectors for the Graphics Bulkhead, which is installed lower in the chassis and connects to it via ribbon cables.

Extreme Graphics

Extreme Graphics is the lowest-end graphics option available for the Onyx. It was also available in the Indigo2, where it was the highest-end option until the introduction of IMPACT graphics in 1995. While Extreme Graphics boardsets are relatively common in Indigo2s, they are a rare and largely undocumented option in the Onyx. While it is generally understood that the graphics boardset itself is identical to the one found in an Indigo2, the hardware used to connect it to the Onyx (which does not normally have GIO64 slots) is poorly documented. Further information about the adapters required for this configuration can be found in the "Architecture" section above. The graphics hardware itself is simply a regular Extreme Graphics boardset (see Indigo2). This configuration is rare, and this, combined with the fact that it is rarely mentioned in official SGI documents, is likely the reason for the scarcity of information surrounding it.

==== I/O ====
The IO4 I/O Controller implements the basic I/O functions for Onyx systems:

* Ethernet Controller
* two fast/wide 16 bit SCSI-2 controllers
* four serial ports (3x RS232, 1x RS422)
* a parallel port
* two Flat Cable Interfaces (for VME or Graphics)

In Onyx Deskside systems 1 IO4 controller can be installed, in rackmount Onyxes up to 6 of these boards can be installed.

== Operating System Support ==
It is recommended to run IRIX 6.5.22 on all revisions/versions of this machine.

=== Troubleshooting ===
No power-on

If a previously working Onyx with no known power supply issues suddenly refuses to power on (specifically no DC GOOD light, no front panel controller functioning) it is possible the Dallas chip located on the System Controller Board (rear access panel of the Onyx) has gone bad. Replacing the Dallas DS12887 with a new production version will allow the system to power on correctly.

=== Links ===

* "RealityEngine Graphics" paper: &lt;nowiki&gt;http://www.sgistuff.net/hardware/graphics/documents/K.Akeley-RealityEngine.pdf&lt;/nowiki&gt;
* "InfiniteReality: A Real-Time Graphics System" paper: &lt;nowiki&gt;http://people.csail.mit.edu/ericchan/bib/pdf/p293-montrym.pdf&lt;/nowiki&gt;

[[Category:Hardware]]</text>
    <sha1>c83558cf142a045bcf161e77db250d56e53dd1ee</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Onyx2</title>
  <ns>0</ns>
  <id>93</id>
  <revision>
    <id>303</id>
    <parentid>182</parentid>
    <timestamp>2025-02-23T17:41:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6581" xml:space="preserve">[[File:Onyx2 Late Logo.jpg|thumb|An onyx2 with the later font]]
For the rack variant, see the [[Origin 2000]] article

The SGI Onyx2, code name ''Kego'', is the successor of the SGI [[Onyx]]. The Onyx2's basic system architecture is based on the Origin 2000, but the midplane and some parts such as the IO6 are different between models. The Onyx2 is notable for the InfiniteReality2, 2E and 3 boards it usually is equipped with, as well as its imposing size, weight and aesthetics.

== Features ==
The Onyx2 deskside form factor can handle up to 4 CPUs distributed across two nodeboards, a maximum of 4 GB of RAM, one GE-16-4, a single DG5-8 for up to 8 displays, and two IR3 or IR4 raster managers for a maximum of 512 MB and 2 GB respectively of texture memory, and can support up to two users simultaneously out of the box. Possibly more with a CADDUO card installed.

A 3-slot PCI cage can be installed as well as a maximum of 10 XIO cards, giving a massive amount of expandability. This is in addition to 5 hard disks and one 5.25 option drive.

==== CPU ====
The following table shows the possible CPU configurations.
{| class="wikitable"
|Processor
|Clockspeed
| colspan="4" |Cache
|-
|R10000
|180 MHz
|1MB
| colspan="3" |R10000
|-
|R10000
|195 MHz
|4MB
| colspan="3" |R10000
|-
|R10000
|250 MHz
|4MB
| colspan="3" |R10000
|-
|R12000
|300 MHz
|8MB
| colspan="3" |R12000
|-
|R12000
|350 MHz
|4MB
| colspan="3" |R12000
|-
|R12000
|400 MHz
|8MB
| colspan="3" |R12000
|-
|R14000
|500 MHz
|8MB
| colspan="3" |R12000
|}

==== InfiniteReality ====
The Onyx2 can handle the following revisions of the InfiniteReality:
{| class="wikitable"
|Model
|GE Revision
|Raster Manager
|Display Generator
|Texture RAM (MB)
|Raster RAM (MB)
|-
|InfiniteReality2
|GE14-4
|RM7-16 or RM7-64
|DG5-2 or DG5-8
|16 to 32
|80 to 160
|-
|Reality
|GE14-2
|RM8-16 or RM8-64
|DG5-2 or DG5-8
|16 to 64
|40 to 80
|-
|InfiniteReality2E
|GE16-4
|RM9-64
|DG5-2 or DG5-8
|64 to 128
|80 to 160
|-
|InfiniteReality3
|GE16-4
|RM10-256
|DG5-2 or DG5-8
|256 to 512
|80 to 160
|-
|InfiniteReality4
|GE16-4
|RM11-1024
|DG5-2 or DG5-8
|1,024 to 2048
|2,560 to 5,120
|}
[[File:Onyx2-raion-passionlip.jpg|left|thumb|An Onyx2 owned by Raion with the cube logo. ]]


InfiniteReality2 is how hinv refers to an InfiniteReality that is used in the Onyx2. The InfiniteReality2 however, was still marketed as the InfiniteReality. It is the second implementation of the InfiniteReality architecture, and was introduced in late 1996. It is identical to the InfiniteReality architecturally, but differs mechanically as the Onyx2's Origin 2000-based card cage is different from the Onyx's Challenge-based card cage.

The Reality is a cost-reduced version of the InfiniteReality2 intended to provide similar performance. Instead of using the GE14-4 Geometry Engine board and the RM7-16 or RM7-64 Raster Manager boards, the Reality uses the GE14-2 Geometry Engine board and the RM8-16 or RM8-64 Raster Manager boards. The GE14-2 has two Geometry Engine Processors, instead of four like the other models. The RM8-16 and RM864 has 16 or 64 MB of texture memory respectively and 40 MB of raster memory. The Reality was also limited by the number of Raster Manager boards it could support, one or two. When maximally configured with two RM8-64 Raster Manager boards, the Reality pipeline has 80 MB of raster memory.

The InfiniteReality2E is an upgrade of the InfiniteReality, marketed as the InfiniteReality2, introduced in 1998. It succeeded the InfiniteReality board set and was itself succeeded by the InfiniteReality3 in 2000, but was not discontinued until 10 April 2001.

It improves upon the InfiniteReality by replacing the GE14-4 Geometry Engine board with the GE16-4 Geometry Engine board and the RM7-16 or RM7-64 Raster Manager boards with the RM9-64 Raster Manager board. The new Geometry Engine board operated at 112 MHz, improving geometry and image processing performance. The new Raster Manager board operated at 72 MHz, improving anti-aliased pixel fill performance.

InfiniteReality3 is the next upgrade and one of the most common for the Onyx2 and Onyx3000 on the secondhand market. The only improvement over the previous implementation is replacement of the RM9-64 Raster Manager with the RM10-256 Raster Manager, which has 256 MB of texture memory, four times that of the previous raster manager.

InfiniteReality4 is the ultimate iteration, introduced in 2002. Primarily used on the Onyx3000 and Onyx350 "G-Bricks". The only improvement over the previous implementation is the replacement of the RM10-256 Raster Manager by the RM11-1024 Raster Manager, which has improved performance, 1 GB of texture memory and 2.5 GB of raster memory, four and thirty-two times that of the previous raster manager, respectively.

Below is a performance table offering comparisons:
{| class="wikitable"
|Reality
|5.5
|94 to 188
| colspan="3" |100 to 200
|-
|InfiniteReality2E
|13.1 to 210
|192 to 6,100
| colspan="3" |200 to 6,400
|-
|InfiniteReality3
|13.1 to 210
|5,600
| colspan="3" |6,400
|-
|InfiniteReality4
|13.1 to 210
|10,200
| colspan="3" |6,400
|}
[[File:Onyx2-rear.jpg|thumb|Rear of an Onyx2, minimally configured]]

==== Memory ====
DIMMs are available in sizes of 16, 32, 64 and 256 MB. The memory modules used in the Origin 200 and Origin 2000 / Onyx 2 are of the same type. To support the Origin 2000 distributed shared memory model, the memory modules are proprietary and include directory memory, which contains information on the contents of remote caches for maintaining cache coherency, supporting up to 32 processors. Additional directory memory is required in configurations with more than 32 processors. The additional directory memory is contained on proprietary DIMMs that are inserted into eight DIMM slots set aside for its use.

==== IO6G ====
An IO6G base I/O board is present in every system. It is a XIO card that provides:

* a 10/100BASE-TX Ethernet port
* 2 sets of PS/2 ports
* 4 Serial ports provided by dual UARTs
* 1 internal Fast 20 UltraSCSI single-ended port
* 1 external wide UltraSCSI, singled ended port
* 1 real-time interrupt output for frame sync
* 1 real-time interrupt input (edge triggered)

Also on the card is the Flash PROM, NVRAM and real time clock of the system.

==== PCI ====
The system can utilize PCI with the addition of an Origin 2000 XIO PCI "Shoebox" or individual XTalk PCI adapters inserted in the cage. These are the same sort form factor as Octane units.

== Operating System Support ==
IRIX Versions from 6.4 to 6.5.30 supported the Onyx2

[[Category:Hardware]]</text>
    <sha1>704345dd3332cfdff53a7065351b781306415522</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Origin 300</title>
  <ns>0</ns>
  <id>62</id>
  <revision>
    <id>304</id>
    <parentid>186</parentid>
    <timestamp>2025-02-23T17:42:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5163" xml:space="preserve">[[File:O300.gif|thumb|Origin 300 rack unit]]
The SGI Origin 300 is a rack-mounted, mid range server sold by Silicon Graphics from 2001 to 2004. The 300 was offered in two to 32 processor configurations, at speeds ranging from 400 to 600MHz over the lifetime of the model. The Origin 300 is not a member of the later Chimera family, though it shares superficial and functional similarities with it. Its closest relative is the [[Fuel]]. 

== Features ==
Each CPU brick has two PCI slots across a PCI bus. All compute bricks are equipped with an IO8 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, and a twisted pair Ethernet connection.

=== CPU ===
Each brick can take dual or quad CPU configurations. The CPUs are attached to the main board, thus a configuration upgrade requires removal of the entire main board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|2MB
|500
|500
|-
|4MB
|600
|600
|}

=== Memory ===
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Fuel, Origin/Onyx350. and the Tezro. There are a total of eight slots, organized into two banks of two slots. This results in a memory capacity from 512 MB to 4 GB total system memory.

All DIMMS for the Origin 300 use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory, which remains unused in the Fuel. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

=== I/O ===
The IO8 card provides SCSI backplane support, and a 100Mbit Ethernet port. Two PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Origin 300 leverages NUMALink heavily to link bricks together. Each unit has a NUMALink and an XIO port, used to link various subsystems together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to eight CPU "bricks" (2 rackmount units high each) with up to four CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink3 cables going to a central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Origin 300 has a front bay for two U160 SCSI drives. It uses proprietary sleds for this purpose.

These sleds are standard off-the-shelf parts used by a number of high-volume server manufacturers, but were apparently only used by SGI on the Origin and Onyx 300 models.

Often Origin 300 systems will be split up and the individual bricks sold to different buyers. While many of these bricks never had hard drives installed, SGI did install sleds with baffles to maintain airflow. This is good news for buyers, as the plastic baffles can be removed and hard drives installed in their place.

The units typically have a sticker on the front of the sled showing the identifier "Assy A06447-00x" where the "-00x" may end in any digit. The second line of the label includes what may be an additional part number ("203368", as seen in the thumbnail image to the right) and a manufacturing code of some kind. It is unclear whether the manufacturing code indicates time of production, plant, batch run, or something else entirely.

However the assembly number from SGI units has not always been useful when searching for replacement parts in the Internet. It was suggested that Intel part number 746797-001 may be the same OEM part.

The 746797-001 part number is referenced in some sources as being used on Intel's SR1200/2200 and ISP2150G servers (black bezel). However images from some eBay auctions appear more similar to the Origin 350-style drive sled, and indeed the Intel product guide for the SR1200 has diagrams showing a unit more similar to that used in the Origin 350.

=== Onyx 300 ===
An Onyx 300 is an Origin 300 NUMALinked to a G-Brick.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator.

=== Operating System Support ===
The Origin 300 was supported beginning with IRIX 6.5.14, and is supported through IRIX 6.5.30

[[Category:Hardware]]</text>
    <sha1>0c40a9042c30df56e763b5c0e8e5508367c65266</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Origin 350</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>305</id>
    <parentid>187</parentid>
    <timestamp>2025-02-23T17:42:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6532" xml:space="preserve">[[File:Origin350 .jpg|thumb|400x400px|Origin 350 Server]]
The SGI Origin 350, and its graphics-equipped sibling the '''Onyx350''', is a rack-mounted, mid range server sold by Silicon Graphics from 2003 to 2007. This system uses MIPS-based processors and offers a number of advances over the [[Origin 300]] model that preceded it. The 350 was offered in two to 32 processor configurations, at speeds ranging from 600 to 1,000MHz over the lifetime of the model. The Origin 350 is a member of the Chimera family (IP53), which includes Origin 350, Onyx 350, and the Tezro Rackmount. All three systems have the same basic hardware - the Origin 350 (Chimera Server) with a VPro card becomes the Onyx 350 (ChiBlade), and the ChiBlade can be configured into a Chimera Rackmount Workstation (Tezro Rack) using the L1's make rmws 1 command. The Chimera Rackmount Workstation cannot accept remote serial numbers, and therefore cannot be connected via NUMALink.

== Features ==
Each CPU brick has four PCI slots across two PCI busses. Each CPU brick also has a Fuel-style XIO slot, which can accept a DMediaPro DM3 card or a VPro graphics card. The first CPU brick in a system has a single PCI slot holding an IO9 BaseIO card with SCSI interfaces for two internal disks, an external SCSI port, audio I/O and a twisted pair Ethernet connection. Other kinds of bricks are available that are dedicated to disk storage or further PCI slots.

The different configurations are:

* Base Compute Module - Includes an IO9, a SCA SCSI backplane (for disks), appropriate cables for disk backplane + IDE CDROM and a daughtercard that provides PS/2 keyboard/mouse and four additional serial ports
* Expansion Compute Modules - These may or may not include the IO9+backplane, but lacks the daughtercard/keyboard/mouse/extra serial ports
* Memory and PCI Expansion (MPX) Modules - Lacks the IO9+backplane and daughtercard/keyboard/mouse/extra serial ports.
* 2UPX Module - PCI Only Expansion Module; a standard 2U Origin 350 chassis with four PCI-X and one XIO-2 slot without processor, memory or Bedrock ASIC. Because the 2UPX does not have a BedRock ASIC, it uses the external XIO port when linked to Origin 350 Compute Modules.

An Origin 350 cannot be booted by itself without the presence of an IO9 card, it requires the IO9 to start up. If a brick lacks it, one must be installed or otherwise the brick must be numalinked.

=== CPU ===
Each brick can take dual or quad CPU configurations the same as the Tezro. The CPUs are attached to the node board, thus a configuration upgrade requires removal of the entire node board.
{| class="wikitable"
| colspan="3" |CPU Configurations
|-
|CPU Cache
|Dual (MHz)
|Quad (MHz)
|-
|4MB
|600,700,800
|600,700,800
|-
|8MB
|700,800
|700,800
|-
|16MB
|1000MHz
|1000MHz
|}

=== Memory ===
On introduction SGI claimed an industry-leading 3.2 GByte-per-second processor to memory bandwidth, and half that to the graphics subsystem. The DIMMS used are compatible with those used in the Origin 3000, Fuel, and the Tezro. There are a total of eight slots, organized into four banks of two slots. This results in a memory capacity from 512 MB to 8 GB total system memory.

All DIMMS for the Origin 350 use Double Data Rate (DDR) synchronous dynamic random-access memory (SDRAM), at the lowest level organized into banks of two DIMMs each - memory may only be added or removed from the system in pairs of two DIMMs. Both DIMMs within a bank must be of the same density, however two different banks may hold different density DIMMs from each other.

SGI produced DIMMs with capacities of 256MB to 1GB, using DRAM chips with densities of either 128 Mbits or 256 Mbits. All DIMMs include directory memory to support cache coherence between local and remote memory. Memory was generally marketed in kits of two DIMMs, where the capacity of the kit would be given as 512MB, 1GB, or 2GB.

=== I/O ===
The IO9 card provides SCSI backplane support, 3.5mm Audio, and a 1Gbit Ethernet port. Three PCI-X slots can provide additional cards, such as network cards, SCSI cards, Firewire, extra audio and more.

Two USB ports and PS/2 are provided. USB Mass storage is not supported for the SGI PROM and by IRIX.

=== NUMALink ===
NUMAlink is a high-speed low-latency switched fabric computer bus used as a shared memory computer cluster processor interconnection in Silicon Graphics computer systems. The Origin 350 leverages NUMALink heavily to link bricks together. Each unit has a NUMALink and an XIO port, used to link various subsystems together.

Multiple bricks are co-ordinated at startup time via an L2 Controller which communicates to the bricks via USB ports. The L2 Controller is an external PowerPC Linux unit with console, USB, modem and ethernet ports.

A system consists of up to eight CPU "bricks" (2 rackmount units high each) with up to four CPUs in each brick, giving a maximum of 32 CPUs. CPU bricks are connected together via NUMAlink3 cables going to a central NUMAlink Router (or NUMAlink Module) which is another 2U rackmounted unit.

=== Storage ===
The Origin 350 has a front bay for two U160 SCSI drives. It uses proprietary sleds for this purpose.

The Origin/Onyx 350, Prism, Altix 350, and Altix 450/4x00 all use the same drive carriers. These are standard parts used by a number of manufacturers, notably Intel's SC5200, SRSH4, SR1300/2300, and SR1400/2400 and Sun's v60x and v65x servers.

The units carry "Assy A65278-00x" on a sticker, where the "-00x" may end in any digit though "-005" seems common. This assembly number can be useful when searching for parts in the Internet. According to SR1300/SR2300 support documents at intel.com, the Intel accessory part number for the drive carrier is FXX2DRVCARBLK, UPC code "7 35858 14621 0" and "MM #" 835853. However note that there is some indication that Intel may recycle these accessory part numbers in the FXX- form between different models.

=== Onyx 350 ===
An Onyx 350 is an Origin 350 with a V10/V12 graphics card attached to the XIO2 slot inside, or an Origin 350 attached to a G-Brick.

=== Hardware Problems ===
The main issue affecting these units is invalid serial numbers, which can be fixed using another brick, an L2 controller, or an L2 emulator called an L3 controller.

It is recommended to use 1GHz boards in the Origin 350, not a Tezro desktop, for the reason of airflow and longevity.

=== Operating System Support ===
The Origin 350 was supported beginning with IRIX 6.5.15, and is supported through IRIX 6.5.30

[[Category:Hardware]]</text>
    <sha1>cdc798104fc23616604c8f9b31af27565208f54c</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Origin 2000</title>
  <ns>0</ns>
  <id>58</id>
  <revision>
    <id>306</id>
    <parentid>149</parentid>
    <timestamp>2025-02-23T17:43:35Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3378" xml:space="preserve">For the graphics deskside variant, see the [[Onyx2]] article
[[File:Origin 2000 Deskside .jpg|thumb|Front view of an Origin 2000 Deskside]]
The SGI Origin 2000, code name ''Lego'', is the successor of the SGI Challenge line. Sold in deskside, rack and multi-rack configurations, the Origin 2000 is a highly modular and scalable system.
[[File:Deskside Oriigin 2000 Profile.jpg|left|thumb|Another view of an Origin 2000 Deskside in profile]]

== Features ==
Each Origin 2000 module is based on nodes that are plugged into a midplane. Each module can contain up to four node boards, two router boards and twelve XIO options. The modules are then mounted inside a deskside enclosure or a rack. Deskside enclosures can only contain one module, while racks can contain two. In configurations with more than two modules, multiple racks are used.

The following table shows a list of models and their possible configurations:
{| class="wikitable"
|Model
|CPUs
|Memory
|I/O
|Chassis
|-
|Origin 2100
|2 to 8
|Up to 16 GB
|12 XIO
|Deskside
|-
|Origin 2200
|2 to 8
|Up to 16 GB
|12 XIO
|Deskside
|-
|Origin 2400
|8 to 32
|Up to 64 GB
|96 XIO
|1-4 Racks
|-
|Origin 2800
|32 to 128
|Up to 256 GB (512 GB unsupported)
|384 XIO
|1 to 9 racks (with Meta Router)
|}
A 3-slot PCI cage can be installed as well as a maximum of 10 XIO cards, giving a massive amount of expandability. This is in addition to 5 hard disks and one 5.25 option drive.

==== CPU ====
[[File:Onyx2 rack.jpg|thumb|An Origin 2000 rack unit is seen here with an onyx2 graphics unit]]
The following table shows the possible CPU configurations.
{| class="wikitable"
|Processor
|Clockspeed
| colspan="3" |Cache
|-
|R10000
|180 MHz
|1MB
| colspan="2" |R10000
|-
|R10000
|195 MHz
|4MB
| colspan="2" |R10000
|-
|R10000
|250 MHz
|4MB
| colspan="2" |R10000
|-
|R12000
|300 MHz
|8MB
| colspan="2" |R12000
|-
|R12000
|350 MHz
|4MB
| colspan="2" |R12000
|-
|R12000
|400 MHz
|8MB
| colspan="2" |R12000
|-
|R14000
|500 MHz
|8MB
| colspan="2" |R12000
|}

=== Memory ===
DIMMs are available in sizes of 16, 32, 64 and 256 MB. The memory modules used in the Origin 200 and Origin 2000 / Onyx 2 are of the same type. To support the Origin 2000 distributed shared memory model, the memory modules are proprietary and include directory memory, which contains information on the contents of remote caches for maintaining cache coherency, supporting up to 32 processors. Additional directory memory is required in configurations with more than 32 processors. The additional directory memory is contained on proprietary DIMMs that are inserted into eight DIMM slots set aside for its use.

==== IO6 ====
An IO6 base I/O board is present in every system. It is a XIO card that provides:

* a 10/100BASE-TX Ethernet port
* 2 Serial ports provided by dual UARTs
* 1 internal Fast 20 UltraSCSI single-ended port
* 1 external wide UltraSCSI, singled ended port
* 1 real-time interrupt output for frame sync
* 1 real-time interrupt input (edge triggered)

Also on the card is the Flash PROM, NVRAM and real time clock of the system.

==== PCI ====
The system can utilize PCI with the addition of an Origin 2000 XIO PCI "Shoebox" or individual XTalk PCI adapters inserted in the cage. These are the same sort form factor as Octane units.

=== Operating System Support ===
IRIX Versions from 6.4 to 6.5.30 supports the Origin 2000.

[[Category:Hardware]]</text>
    <sha1>406e621e6211bcf1aefab934e1cd48aab4d86f79</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Octane</title>
  <ns>0</ns>
  <id>70</id>
  <revision>
    <id>307</id>
    <parentid>183</parentid>
    <timestamp>2025-02-23T17:43:58Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9273" xml:space="preserve">[[File:An Octane2 setup.jpg|thumb|An Octane2 setup]]
The Octane and its later version, the '''Octane2''', code named Speed Racer, is a high end workstation marketed by Silicon Graphics between 1996 and 2004. Replacing the [[Indigo2]], it is an SMP-capable (dual CPU) machine running the MIPS R10000 to R14000 series of processors. The main differences between the Octane2 and the Octane are configuration-related. The Octane 2 has upgraded motherboard, power supply, front plane and graphics options, but it's entirely possible to retrofit these upgrades to a regular Octane, creating the "Octane 1.5" as many have popularly dubbed it. 

== Features ==
[[File:Octane-new-logo.jpg|left|thumb|An Octane late model with the "sgi" logo]]
The Octane's system-board is designated as IP30. The system is based on SGI's Xtalk (Pronounced Cross-talk) architecture. This means it does not use a system bus; instead it has a router XBOW (Pronounced cross-bow) that connects any two of its ports. One of the ports is used for the processor and memory subsystem, one is available for PCI (actually PCI-64) expansion and four are XIO slots (packet-based high-bandwidth bus, somewhat similar to HyperTransport). This makes it very similar to a single node of the SGI Origin 200 system.

The XIO is here and there bridged to PCI-64, using a chip named BRIDGE. The places where it happens include the system board (for the IOC3 multi-I/O chip, two ISP1040B SCSI controllers and RAD1 audio), MENET cards (four IOC3s) and the PCI cage (used for PCI cards in Octane). ARCS is provided as the boot firmware, similar to all contemporary SGI computer systems.

==== CPU ====
The Octane series has single and dual CPU modules. A second CPU cannot be added to a single CPU module, therefore upgrading to two requires replacing the entire CPU module.

What follows is a table of all known models:
{| class="wikitable"
|Processor
|Cache
|Single (Mhz)
|Dual (Mhz)
|-
|R10000SC
|1MB
|175, 195, 225, 250
|175, 195, 225, 250
|-
|R12000SC
|2MB
|270, 300, 400
|270, 300, 400
|-
|R12000SCA
|2MB
|360, 400
|360, 400
|-
|R14000SCA
|2MB
|550, 600
|550, 600
|}

==== Memory ====
The Octane allows 256 MB to 8 GB of system memory, using proprietary 200-pin DIMMs. There are two system board revisions. The first revision (part number 030-0887-00x, usually distinguished by a black handle) only supports 2GB of RAM while the later one (part number 030-1467-001, with a silver handle) supports up to 8GB. The -0887 revision of the mainboard will work with all 32-128 MB DIMMS and the stacked variant of 256MB DIMMS, but not the later single-board version (SGI P/N 9010036). The memory subsystem has vast reserves of bandwidth that can be directly served by the Xbow router to any XIO card.

The Octane's memory controller is aptly named HEART. It acts as a controller between the processor, the memory (SDRAM) and the XIO bus.

==== Graphics ====
Graphics on the Octane are provided by a series of cards: SI, SI+T, SSI, MXI. These are updated XIO versions of Solid Impact (SI), High Impact (SI+T) and Maximum Impact (MXI) from the SGI Indigo2 that were internally designated by SGI as 'MARDIGRAS'. The boards were accelerated and reengineered with faster geometry engine and texture modules to create their new versions: SE, SE+T, SSE, MXE. The SI/SE provides 13.5MB of framebuffer memory while the SSE and MXE have a 27MB framebuffer. The '+T' indicates an additional high speed RDRAM texture board which gives 4MB of texture memory, which is practically indispensable, though quite expensive and fragile. The SI/SE+T has one texture board while the MXI/MXE has 2 texture boards, however, the 2 boards in the MXI/MXE do not double the available texture memory to the system. It just doubles the texture performance.

Later Octanes and Octane 2s support the SGI VPro graphics board series, designated 'ODYSSEY'. The first VPro series cards were the V6 and V8. The main differentiator being that the V6 has 32MB of RAM (unlike the MARDI GRAS option, framebuffer memory and texture memory come from the same pool) and V8 having 128MB. Later, the V10 (32MB) and V12 (128MB) were introduced. The main difference with the new VPro V10/V12 series is that they had double the geometry performance of the older V6/V8. V6 and V10 can have up to 8MB RAM allocated to textures (2X more than the textured-enabled MARDIGRAS options), while V8 and V12 can have up to 108MB RAM used for textures.

The VPro graphics subsystem consists of an SGI proprietary chip set and associated software. The chip set consists of the buzz ASIC, pixel blaster and jammer (PB&amp;J) ASIC, and associated SDRAM.

The buzz ASIC is a single-chip graphics pipeline. It operates at 251 MHz and contains on-chip SRAM. The buzz ASIC has three interfaces:

* Host (16-bit, 400-MHz peer-to-peer XIO link)
* SDRAM (The SDRAM is 32 MB (V6 or V10) or 128 MB (V8 or V12); the memory bus operates at half the speed of the buzz ASIC.)

* PB&amp;J ASIC

As with the MARDIGRAS boards, all VPro boards support OpenGL in hardware (MARDIGRAS is OpenGL 1.1 + SGI Extensions, while VPro upgraded support to OpenGL 1.2) and OpenGL ARB imaging extensions, allowing for hardware acceleration of numerous imaging operations at real-time rates.

Compatibility: The V6/V8 boards require an XBOW 1.3 board, but the V10/V12 boards do appear to require an XBow 1.4 frontplane.

==== I/O and HEART ====
The Octane supports Ultra Wide SCSI devices and has two SCSI controllers. System can have up to three internal 3.5" SCSI SCA devices. Octanes use special mounting sleds for the hard drives which are compatible with Origin 2000, Origin 200 and Onyx2. The system also has external Ultra Wide SCSI bus.

The aptly named HEART is the core of the Octane. It integrates a SDRAM memory controller, a XIO device, an interrupt controller and a processor bus interface for up to four R10000-class processors.

The HEART can be accessed in two ways from the processor. The first one is through the PIU (Programmed I/O Unit) at 0xFF0000 in processor physical address space. The other one is at widget 8 in XIO address space. The only one way available to other XIO devices is through the widget interface, so the Interrupt Status Set register is mapped there at address 0x80.

The HEART contains a SDRAM memory controller with ECC. ECC errors are signaled to the CPUs by interrupts.

The XIO bridge is one of the main functions of the HEART. There are three access windows defined for each XIO widget number. There is a window at 0x10000000+ W*0x1000000 for widget number W, a window at 0x800000000+W*0x80000000 and a window at 0x1000000000+W*0x1000000000.

Note that XIO accesses are deeply pipelined by default. Due to that fact, writing to any XIO widget may not have any effect for several hundred cycles. To guarantee finalization of all posted writes it is required to read the widget flush register.

The XIO bridge in HEART provides also some Flow Control features for two channels. They allow to schedule a hiwater IRQ for any given XIO register address. If the register is an input to a FIFO, as is the case with the IMPACT graphics board, exceeding a prescribed number of writes to this register would cause a FIFO hiwater condition. As you already know, the XIO writes are posted and not immediately executed. Catching the hiwater condition in the HEART and not in the card allows to trap it in a more reliable way.

The HEART interrupt controller is visible from the PIU as a set of registers: interrupt mask registers for all processors (IMR0:3), an interrupt status register (ISR) and ISR clear and set registers that allow atomic manipulation of the ISR.

The XIO side consists of a single register 0x80 that can accept either an atomic ISR bit set command or an atomic ISR bit clear command. These commands cause asserting and deasserting IP7:2 bits in the CPUs whose IMRs contain the bit in question.

A small part of the HEART is a programmable interval timer, consisting of 24-bit COUNT and COMPARE registers. The IRQ can be delivered only to the IP6 bit, which is the highest-priority CPU interrupt except internal CPU timer and HEART error IRQs. The timer counts at 12.5 MHz, every 8th internal HEART cycle (1/4th of the XIO frequency).
[[File:Octane2.jpg|thumb|Another view of an Octane2]]
The HEART controls also the Number In a Can associated with processor modules. It features a standard SGI issue MicroLAN controller. 

== Octane 2 Upgrades ==
Octane 2 has a revised power supply, system-board and XBOW. Octane 2 also shipped with VPro graphics and supports all available VPro cards (V6, V8, V10 and V12). Later revision Octanes also included some of the improvements mentioned.

The case is blue instead of the green used by the original, the plastics are compatible between the two and the chassis is identical.

=== Operating System Support ===
The Octane was first supported by IRIX version 6.4 with IMPACT or "Mardi Gras" graphics (SI/SSI/MXI and later Enhanced versions). Support for VPro or "Odyssey" graphics in Octanes was introduced with IRIX 6.5.10 for V6/V8, and in IRIX 6.5.11 for V10/V12. (Drivers were released to support V10/V12 under 6.5.10.) All versions of IRIX through 6.5.30 include support for the Octane family machines.

[[Category:Hardware]]</text>
    <sha1>153c96064435a6dae4945515a0a3352e87bc29d8</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>O2</title>
  <ns>0</ns>
  <id>74</id>
  <revision>
    <id>308</id>
    <parentid>184</parentid>
    <timestamp>2025-02-23T17:44:15Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9504" xml:space="preserve">The Silicon Graphics O2, codename Moosehead, is an entry-level Unix workstation introduced in 1996 by Silicon Graphics, Inc. (SGI) to replace their earlier [[Indy]]. Like the Indy, the O2 uses a single MIPS microprocessor and was intended to be used mainly for multimedia. Its larger counterpart was the SGI [[Octane]]. The O2 was SGI's last attempt at a low-end workstation.

== Features ==
O2 features a proprietary high-bandwidth Unified Memory Architecture (UMA) that connects the various system components. The O2 is a highly-integrated system, with CPU, graphics accelerator, memory, SCSI controller, and I/O all incorporated into a single system module, which can be slid out of the chassis with the flip of a lever. A PCI bus is bridged onto the UMA with one expansion slot available. The O2 has a designer case and a modular design, with space for two Ultra SCSI drives mounted on special sleds (only one in the later R10000/R12000 models) and an optional video capture / sound module mounted on the far left side. Further information on the design and construction of the O2 can be found in SGI service manuals on Techpubs. Detailed breakdown pictures and an IRIX hinv dump can be found here.

An O2's unique system ID (MAC address) is stored on the small PCI riser card that connects the PCI card holder to the motherboard. If this riser card is swapped, the corresponding black plastic badge on the rear of the case should be swapped as well to preserve consistency.

WARNING: The O2 system module should NEVER be removed or installed while the power cord is connected. Doing so can permanently damage the motherboard.

==== CPU ====
The O2 comes in two distinct CPU flavours; the low-end MIPS 180 to 350 MHz R5000- or RM7000-based units and the higher-end 150 to 400 MHz R10000- or R12000-based units. The 200 MHz R5000 CPUs with 1 MB L2-cache are generally noticeably faster than the 180 MHz R5000s with only 512 KB cache. There is a hobbyist project that has successfully retrofitted a 600 MHz RM7xxx MIPS processor into the O2.

There is also a hobbyist project that has successfully retrofitted a 600 MHz R7000 MIPS processor into the O2. In theory faster CPUs at 900MHz any beyond are possible, but this would require the public release of the O2 PROM source code which at present is not available and probably never will be.
[[File:O2 full setup.jpg|thumb|An O2 in full setup]]
A recall of some early versions of the RM7000A 350Mhz CPU is thought to have hastened the removal of the O2 from SGI's product line.

==== Memory ====
There are eight DIMM slots on the motherboard and memory on all O2s is expandable to 1 GB using proprietary 239-pin SDRAM DIMMs. The Memory &amp; Rendering Engine (MRE) ASIC contains the memory controller. Memory is accessed via a 133 MHz 144-bit bus, of which 128 bits are for data and the remaining for error-correcting code (ECC). This bus is interfaced by a set of buffers to the 66 MHz 256-bit memory system.

Original SGI-branded O2 DIMMs are either single-sided (SS) with memory chips on only one side of the module or double-sided (DS), and are color-coded to assist in identification. 3rd party DIMMs may or may not follow these conventions. Knowing the current memory configuration is important as DIMMs must be installed according to a number of specific rules.

* The DIMMs in slots 1 and 2 make up Bank A. DIMMs in slots 3 and 4 make up Bank B, and so on.
* A bank of two slots must have a DIMM in each slot or be empty (except for slots 1 and 2, Bank A, which must always be populated.)
* The two DIMMs in any bank must be of the same size and type.
* The largest size DIMMs must be in Bank A.
* DIMM banks must be filled sequentially, beginning with bank A.
* Equal or smaller size DIMMs must be in Bank B, and so on.
* Do not skip banks, or the memory will not be recognized.

To install high density (128 MB) DIMMs, PROM revision 4.4 or higher is required. With older PROM revisions maximum memory is 256 MB. For IRIX 6.3 there are patches to upgrade the PROM as described in "Silicon Graphics® O2® Workstation Memory Installation Instructions", for IRIX 6.5 PROM images come with the operating system and overlays CD sets.

==== Graphics ====
[[File:SGI O2.jpg|left|thumb|An early-model O2 with the original cube logo]]
The CRM chipset that SGI developed for the O2 shares OpenGL calculations with the CPU. Due to the unified memory architecture, video memory is shared with main memory, and there is effectively an 'unlimited' amount of texture memory. Another useful feature is that any incoming video data from the Audio/Video option can be mapped directly as an OpenGL texture without having to perform a copy or move.

ICE (Image Compression Engine — a dedicated 64-bit R4000-based processor containing a 128-bit SIMD unit running at 66 MHz, which is used to accelerate various image and video operations)

The O2 Video system supports two simultaneous input video streams and one output video stream which can be separated into two outputs, one carrying pixel information, the other carrying alpha (key) information.

Using the O2 Video system, it is possible to capture live video into the computer's memory which can then be displayed in a graphics window on the screen or further processed by an application. It is also possible to generate video output from images in memory, which can be displayed on a standard video monitor, or recorded to a VTR. Using the VL programming library, a program can capture video in either the RGB or YCrCb color spaces, and either full or reduced size formats, and in a format usable for input to the compressor/decompressor, display on the graphics screen, or as an input to a graphics processing and/or texture operation.

SGI offered two video options for the O2/O2+: the AV1 interface and the AV2 interface.

The AV1 interface supports Composite and S-Video (Y/C) (both analog), and Digital I/O via the Camera/Digital Video port. The analog I/O jacks are for use with standard analog video equipment, supporting both PAL and NTSC video formats. There are a variety of controls available that allow the user or programmer to set various parameters used for the decoding and encoding of the video signals. The digital input of the AV1 is for use with the O2Cam Digital System Camera, or can be connected to an optional digital video input and output adapter to interface to standard SMPTE259M serial digital video devices.

The AV2 interface supports two ITU-601 (CCIR-601) serial digital video input connectors and two similar output connectors, as well as GPI input and output and analog (black burst) sync input and loop through.

==== I/O ====
I/O functionality is provided by the IO Engine ASIC. The ASIC provides a 33-bit PCI-X bus, an ISA bus, two PS/2 ports for keyboard and mouse, and a 10/100 Base-T Ethernet port. The PCI-X bus has one slot, but the ISA bus was present solely for attaching a Super I/O chip to provide serial and parallel ports.

=== O2+ ===
[[File:SGI O2+ by Mattst88.jpg|thumb|An O2+, property of mattst88]]
The O2+ is a special variant of the SGI O2 with a purple/grey color scheme, top of the line multimedia, CPU and memory. It was produced in very low quantities and has remained a valuable item for collectors, selling for many times the going rate for O2s on average.

=== Operating System Support ===
IRIX versions 6.3 and 6.5 (up to the latest overlay - 6.5.30) are supported on this machine, however, only in 32-bit mode, due to the nature of the O2's internal architecture. For CPU-specific versions, see also: IRIX for O2.

Besides the default CD-based Installation, the O2 also supports network installation.

=== Hardware Problems ===
The Toshiba CD-ROM drives in the O2 commonly throw a small white plastic gear from the tray motor. Symptoms include the tray either refusing to open or refusing to stay closed. This problem is relatively easy to fix by opening the CD-ROM drive and pushing the gear back onto the motor shaft, then adding a small amount of glue to keep the gear in place. To avoid damaging the tray mechanism during ordinary use, do not push it closed: use the "inject" command instead.

To quote kjaer in a Nekochan forum post &lt;nowiki&gt;https://web.archive.org/web/20170821000034/http://forums.nekochan.net/viewtopic.php?f=3&amp;t=16726667&lt;/nowiki&gt; "...there is a pressfit nylon pinion on the transport motor that opens and closes the drive tray, and also raises and lowers the optical pickup assembly (moves it closer to the disc after the tray closes, and moves it away from the disk before the tray opens). This pinion splits when it ages, and when this happens the static friction between pinion and spindle is no longer sufficient to hold the torque required to lift the optical pickup. The drive interprets this as a mis-load and ejects the tray." A further discussion with images can be found &lt;nowiki&gt;https://web.archive.org/web/20170820231441/http://forums.nekochan.net/viewtopic.php?f=3&amp;t=16727779#p7360973&lt;/nowiki&gt;

==== Memory ====
The O2's proprietary memory modules are highly susceptible to dirt and shock, particularly during shipping. The symptoms of a bad memory contact include random memory errors and a total inability to boot, with a solid red or blinking amber LED at startup. Careful cleaning and re-seating of memory will typically solve such problems, though the DIMMs should also be carefully inspected for missing surface-mount components, which can be easily knocked-off via mishandling.

[[Category:Hardware]]</text>
    <sha1>12ae94937a68096d6e8f7f0fe220554e05ce7e8f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Indy</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>309</id>
    <parentid>179</parentid>
    <timestamp>2025-02-23T17:44:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Features */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7100" xml:space="preserve">[[File:Indymag.jpg|thumb|500x500px|SGI Indy owned by CB_HK]]
The Indy, code-named "Guinness", is one of the low-end workstations by Silicon Graphics. Selling for around $5000 USD at base price it was one of the cheaper models. It is notable for its common-ness, comparable to the Amiga 500 for Amigas, and its use in development for the Nintendo 64. It was introduced on July 12, 1993 to replace the low end models of the [[IRIS Indigo]] and discontinued on June 30, 1997.

== Features ==
The Indy is a small desktop (dimensions 41 x 36 x 8 centimetres) computer consisting of a steel frame with a removable bright blue plastic skin. The system is capable of supporting the weight of a small CRT or a modern LCD/LED monitor without damage.

After removing the plastic skin, the power supply, long, thin and bolted to the side of the computer is visible, along with the motherboard, any 3.5" hard disks or the optional Floptical drive, along with the GIO riser and video card, as well as both expansion ports.

==== CPU ====
The processors are supplied on a "Processor Module" board with or without external cache (Primary Cache means no external cache, Secondary Cache means there is an external cache) and range from a 100MHz R4000 to a 180MHz R5000.

Indy's motherboard has a socket for the Processor Module (PM). Early Indys used the 100 MHz MIPS R4000 CPU, which quickly proved inadequate. The Indy, at the bottom of SGI's price list, thus became the primary platform for MIPS's low-cost, low-power-consumption R4600 CPU series. The R4600 had impressive integer performance, but had poor floating-point capability. This, however, wasn't too huge of a problem in a box that was generally not designed for floating-point-intensive applications. For this reason, the R4600 made an appearance outside the Indy line just once, and only briefly, in the Indigo 2. This series of CPU issues, along with the relatively low-powered graphics boards, lower maximum RAM amount, and relative lack of internal expansion ability compared to the Indigo led to the Indy being pejoratively described amongst industry insiders as "An Indigo without the 'go'."

The R4600 chip itself has no L2 cache controller, external controller was used to add 512K of L2 cache. R4600s processor modules both with an L2 cache (SC) and without (PC) are common in the Indy. At the same clock rate, the SC version of the processor module is generally 20 to 40 percent faster than the PC version, due to the memory cache.

The Indy was also the first SGI to utilize the MIPS R5000 CPU, which offered significant advantages over the R4400 and R4600 it replaced. The Indy's 180 MHz R5000 module can be overclocked to 200 MHz by replacing its crystal oscillator chip.

==== Memory ====
The system takes standard 72-pin SIMMS (gold plated SIMMS are recommended to avoid dielectric corrosion) and can take anywhere from as low as 16MB to 256MB, these must be added in sets of 4 at a time since the computer is 64-bits and each SIMM is a 16-bit module.Upon release, the base configuration came at 16MB. IRIX 5.1, the first Operating System for the Indy, did not take full advantage of the hardware due to inadequate memory management and the 16MB configuration failed to even boot. SGI quickly increased the base specification to 32 MB, and shipped free memory upgrades at considerable cost. Subsequent IRIX releases made huge improvements in memory usage.

==== Graphics ====
Graphics are one of three possible types: 8-bit XL, 24-bit XL, and XZ. The 24-bit XL card is the most desirable for collectors due to its decent 2D performance and better than the XZ 3D performance when combined with an R5000 CPU. All three options use the 13W3 connector and require a Sync on Green monitor.

The Indy includes analog and digital video inputs, such as Composite and S-Video, as well as a proprietary digital D-sub used by the Indycam. The system is capable of capturing video at a maximum resolution of either 480i or 576i, depending on region.

It takes a fast machine to capture at either of these resolutions, though; an Indy with slower R4600PC CPU, for example, may require the input resolution to be reduced before storage or processing. However, the Vino hardware is capable of DMAing video fields directly into the framebuffer with minimal CPU overhead.

None of the Indys support video output by default - that would require the Indy Video GIO32 card. In addition, there is an optional video module called CosmoCompress, which offers realtime JPEG video compression and decompression and uses up another GIO32 slot.

==== Networking ====
For networking, the Indy has an on-board AUI, an ISDN port, and a 10Mb Ethernet jack. The AUI and Ethernet cannot be used at the same time, the Ethernet jack takes priority automatically. 10/100Mb cards are available on the used market for faster connection speeds.

==== Storage ====
The Indy has two drive bays for 1-inch tall 3.5" drives. The upper drive bay is externally accessible and may hold a SCSI floptical drive. All external and internal drives share a single Fast SCSI bus (unless a GIO32 SCSI card has been installed). External CD-ROM drive connect via SCSI connector at rear side of the box. Typical drive supports boot, OS install, audio. Special ROM is required to boot from for certain device types.

=== Operating System Support ===
The Indy's basic support came in IRIX 5.1 but that is not a recommended release. The Indy is supported through IRIX 6.5.22, it is recommended to use one of the following releases:

* IRIX 5.3
* IRIX 6.2
* IRIX 6.5.22

IRIX 6.5.22 has the most software available, but will be slow on systems below 128MB. 6.2 and 5.3 are much lighter weight, but have their own limitations.

=== Hardware Problems ===
The component of the Indy most prone to failure is the power supply. Neither the Sony nor the Nidec varieties are more reliable, and both have benefits and drawbacks.

==== MAC/System Serial ====
The Indy's Ethernet address, which doubles as the system's serial number, is stored in battery-backed RAM. This means that when the internal battery dies, so does the system - it will hang at the PROM monitor and refuse to boot any further as a result of the Ethernet address being all FFs. A non-amateur user can replace the PROM battery and reprogramme it. The original battery was made by Dallas Semiconductor, now owned by MAXIM. The original unit was marked the "DS-1386-8K-150", however its replacement unit, the "DS-1386-8K-120" can be directly substituted with no ill effects.

To reset the MAC, it's necessary to use fill commands:

To set the MAC 08:00:69:08:e2:0a, for example, this would be done from the PROM:&lt;pre&gt;
fill -w -v 0x08 0xbfbe04e8

fill -w -v 0x00 0xbfbe04ec

fill -w -v 0x69 0xbfbe04f0

fill -w -v 0x08 0xbfbe04f4

fill -w -v 0xe2 0xbfbe04f8

fill -w -v 0x0a 0xbfbe04fc
&lt;/pre&gt;The MAC address is (usually) on a sticker to the rear of the unit, and hence can be reprogrammed without losing software licenses, which often rely on it to verify ownership. Otherwise, any MAC address in SGI's block is usable.

[[Category:Hardware]]</text>
    <sha1>ff3897855f52c2249df01bbb14050dcb4ef51953</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Indigo2</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>310</id>
    <parentid>180</parentid>
    <timestamp>2025-02-23T17:44:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4542" xml:space="preserve">The Indigo 2, codenamed "Fullhouse" is a high end workstation marketed by Silicon Graphics from 1993 to 1997, with production of IMPACT models ending in 1998. The Indigo 2 succeeded the earlier [[IRIS Indigo]]&lt;nowiki/&gt;line and is the higher end version of the [[Indy]].

== Features ==
The Indigo 2 is a large teal or purple desktop that is deceptively heavy, around 40lbs. It came with two plastic feet which can be used to set it upright vertically.

==== CPU ====
The Indigo 2 has three distinct variants, each with a specific motherboard and "IP" number or designation:

* IP22 supports an R4000, R4400, or R4600 CPU clocked at 100-250MHz
* IP26 supports the R8000 CPU clocked at 75MHz
* IP28 supports the R10000 CPU clocked at either 175 or 195MHz

IP26 systems were generally referred to as the POWER Indigo 2, while the IP28 systems usually had a grill badge that read "10000."
[[File:Indigo2-purple.jpg|left|thumb|Indigo2 Impact with an R10000]]

==== Memory ====
All three variants had 12 SIMM slots on the motherboard, organized into three banks of four slots each, and took industry standard fast page mode (FPM) 72 pin SIMMs with parity. Speeds should be 60 or 70 nanoseconds, and the internal organization must be 36 bits wide - 8MB x 72 bit parts will not work.

IP22 systems will support up to 384MB with 32MB SIMMs. While the IP26 and IP28 systems both support 64MB SIMMs, published limits for these systems reflected concerns about the amount of heat generated by then-current DRAM chips. According to SGI the R8000-based IP26 systems would only support 640MB (2 banks of 256MB, one of 128MB), while the R10000-based IP28 would support 768MB (3 x 256MB).

Eventually 64MB SIMMs became available that generated less heat, and denser 128MB SIMMs became available. Both the IP26 and IP28 can use these 128MB SIMMs, but with limitations. IP26 systems require some banks to use lower-profile SIMMs to clear the CPU carrier, and SGI described limits on the mix of different density SIMMs in these systems. However owners have reported working configurations of up to 896MB (1 x 128MB, 1 x 256MB, 1 x 512MB bank).

With the IP28 it is possible to achieve a total of 1GB of RAM (2 banks x 512MB, or 2 x 256MB + 1 x 512MB), but unfortunately this appears to be a hard limit based on address logic.

==== Graphics ====
The graphics boards available for the Indigo 2 were the pre-IMPACT Newport and Express boards (which included the SGI XL24, SGI XZ, SGI Elan and SGI Extreme) and the MGRAS IMPACT boards (the SGI Solid IMPACT, the SGI High IMPACT, the SGI High IMPACT AA, and the SGI Maximum IMPACT). IMPACT graphics is not supported by the Power Indigo 2 (R8000 CPU). The Indigo2's replacement, the SGI Octane, offered an upgraded bus but featured the same graphics options, albeit in repackaged form.

The IMPACT units are purple, though it is feasible to upgrade a teal Indigo 2 with proper upgrade parts.An IMPACT-ready Indigo 2 must have an IMPACT-ready riser card, an IMPACT-ready power supply, and a sufficiently recent PROM revision.

==== Networking ====
For networking, the Indigo 2 has an on-board AUI and a 10Mb Ethernet jack. The AUI and Ethernet cannot be used at the same time, the Ethernet jack takes priority automatically. 10/100Mb cards are available on the used market for faster connection speeds. This is near identical to the Indy's configuration.

==== Storage ====
The internal drive bays of the Indigo2 take model-specific carriers. These carriers mate to a backplane using a non-standard connector, and contain devices using a standard 50 pin IDC ribbon cable connector. There may not be enough room in the carrier to use an adapter board to use 68 or 80 pin devices unless using a down-sized device, e.g. a 2.5" hard drive in a 3.5" drive carrier.

=== Operating System Support ===
The first Indigo 2 systems were introduced during the 4D1-4.x era. These were based on the R4000 microprocessor and featured Express graphics (Elan, XZ). Support for new hardware was added in future releases during this period and later on in the 4D1-5.x era.

Major milestones include the introduction of the Impact graphics options as well as the step from the R4000 to the R10000 CPU. For Impact graphics special versions of the IRIX 5.3 and IRIX 6.2 release were offered. Similarly a special release of IRIX 6.2 was made for the R10000 CPU upgrade.

General support for all Indigo 2 variants can be found in the all platform IRIX 6.5. The support for the remaining legacy systems like the Indigo 2

[[Category:Hardware]]</text>
    <sha1>20ff348a2f4cac4292c736244cd2875fe074440d</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Crimson</title>
  <ns>0</ns>
  <id>42</id>
  <revision>
    <id>311</id>
    <parentid>178</parentid>
    <timestamp>2025-02-23T17:45:04Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5137" xml:space="preserve">The IRIS Crimson or simply Crimson is the partial successor to the [[Power Series]], first released in 1992. It was the first SGI workstation released with a 64-bit processor.
[[File:IRIS Crimson.jpg|thumb|A typical IRIS Crimson]]
The Crimson was a member of Silicon Graphics' IRIS 4D series of deskside systems; it was also known as the 4D/510 workstation. It was similar to other SGI IRIS 4D deskside workstations, and could utilize a wide range of graphics options (up to RealityEngine). It was also available as a file server with no graphics. 

== Hardware ==
* One superpipelined MIPS 100 MHz R4000 or 150 MHz R4400 processor.
* Seven high performance 3D graphics subsystem options deliver performance and features to match any application.
* Up to 256 MB memory and internal disk capacity up to 7.2 GB, expandable to greater than 72 GB using additional enclosures.
* High performance I/O subsystem includes four VME expansion slots, Ethernet and two SCSI channels with disk striping support.
* Seven graphics configurations:

* S, no display, server only
* Entry (LG1/2 board) with VME adaptor*
* Express with VME adaptor*
* ELAN with VME adaptor*
* "Clover2": GTX and GTX(B) boardset
* "Powervision": VGX and VGXT boardset
* "Venice": RealityEngine boardset

&lt;nowiki&gt;*&lt;/nowiki&gt;These boards are identical to the IRIS Indigo

=== Notes ===
The memory modules used in the Crimson are the same as on the MC2 memory board used by the Power Series. However, unlike other IRIS 4D series machines an MC2 board is not recognized by the system. All memory (up to 256MB) must be installed on the IP17 mainboard.

The minimal system configuration consists of two cards: IP17 (CPU mainboard) and IO3B (Input/Output mainboard)

While the MIPS R4000 is a 64-bit processor, the Crimson is only capable of running it in 32-bit mode.

IRIS Crimson can operate with IRIX 6.2, but there are bugs in fx.IP17 in the IRIX 6.2 release. In order to prepare a drive you will either need an earlier version of fx, or you must run fx on another system to partition the drive first.

=== Components ===

==== IP17 ====
The CPU mainboard supports either a 100MHz R4000 or 150MHz R4400 CPU with 1MB L2 memory cache and the memory sub-system.

The bus frequency is half of the core speed, either 50MHz or 75MHz depending on the CPU installed.

The differences between the two versions include the PROM revision and different logic on the board.

The Crimson does not support an MC2 board, any memory up to the maximum amount of 256MB must be installed on the IP17 board.

The Crimson supports only one IP17 board unlike its successor, the rackmount Onyx, which supports multiple CPU boards depending on configuration (the deskside Onyx only supports one CPU mainboard but with multiple processors)

==== I03B ====
The Input/Output mainboard supports the following:

* 2 SCSI channels driven with Western Digital 33C93--one internal device connection and one external device connection
* 2 Centronics connectors on the chassis
* 4 serial ports
* 1 parallel port
* 1 AUI 10Mb ethernet port
* 3 powered peripheral ports (8 Pin DIN)

==== Graphics Subsystems ====
The Crimson could be outfitted with seven different graphics setups depending on the end-user's desired needs. Users seeking a file server could opt for no graphics option, which would mean relying on a terminal or network connection to manage the system as there is no basic graphics capability built into the IP17 or IO3B boards. The six other options consisted of varying levels of performance, ranging from Entry graphics, all the way to RealityEngine. These graphics systems were independent of the IP17 and IO3B boards and could be swapped out in order to provide more or less capability as required.

=== Y2k Bug ===
As the IRIS Crimson had already been replaced by the Onyx and Onyx2 prior to the year 2000, little to no work was done to patch the system prior to the turn of the millennium. While the Crimson is not Y2K proof, the error it encounters is not fatal and can easily be rectified by adding a daemon to startup that will sync the time via NTP and reset the Crimson's internal clock. Failure to re-sync the time will cause the system to gain at least one year each time it is restarted until it reaches the end of the Unix epoch at which time it will cycle back. This has the potential for corrupting files and causing licenses to expire prematurely.
[[File:Crimson-jurassic-classic.jpg|thumb|A "Jurassic Classic" Crimson]]

=== In Popular Culture ===
An IRIS Crimson appeared in the main operations center of Jurassic Park. During one scene in the film, the granddaughter of the park's creator, Lex, used the machine to navigate the filesystem of IRIX 4.0 using the application FSN in order to reactivate the locks on the operations center doors. The increase in popularity of the Crimson following the release of the movie prompted Silicon Graphics to release a special edition model referred to as the "Jurassic Classic." It was notable for being marked as such on the outside of the case, in addition to being signed by Silicon Graphics founder Jim Clark.

[[Category:Hardware]]</text>
    <sha1>01b9cc75d020fe84a621b4e01f855b06576376f5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>IRIS Indigo</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>312</id>
    <parentid>177</parentid>
    <timestamp>2025-02-23T17:45:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5585" xml:space="preserve">The SGI Indigo (Also known widely as the IRIS Indigo) is a line of high end workstations using the MIPS processor family released as a successor to the [[Personal IRIS]] series.

The Indigo R4000 was also the first SGI workstation that that featured the 64bit R4000 RISC CPU on the desktop, the first SGI in general using the new CPU was the [[Crimson]]. The Indigo offers builtin audio capabilities and comes in a very well designed and space efficient chassis. With one of the Express graphics options it offers accelerated 3D graphics.
[[File:Indigo2-mag.jpg|thumb|IRIS Indigo owned by CB_HK]]

== Hardware ==
* One 32-bit R3000 at 33MHz or a R4000 at 100MHz, or a R4400 at 150MHz.
* A maximum of 96MB RAM on R3000 boards (IP12), and 384MB on R4x00 boards (IP20)
* Two GIO32 slots for expansion boards.
* A Motorola 56000 DSP-driven Audio system.
* Seven different graphics options:

* Entry (LG1/2 board)
* Express (XS8, XS24, XS24Z, XZ, Elan)

=== Peripherals ===
The Indigo, unlike later SGIs, does NOT possess support for PS/2 and uses the same keyboard as the SGI Onyx and Crimson. To use PS/2 peripherals necessitates an adapter.

The graphics board uses the 13w3 connector which requires a SOG compliant monitor.

=== Storage ===
All Indigo systems have three drive bays for internal 3.5" SCSI devices that have to be mounted on special drive sleds to be used in the systems. The upper two of them can be accessed from the outside through a small door which makes them usable for removable media drives. To remove any of the three drives the front plate has to be removed which is impossible if the system is secured with the locking bar.

The skins of the Indigo are colored in a dark blue which has a decent hint of purple to it. On R3000 Indigos the type of the graphics option the machine was shipped with was printed on the front door. On R4000 a small badge was used that in addition to the name of the graphics option included "4000" to denote the faster CPU type.

=== Operating System Support ===
The Indigo when first introduced was based on the R3000 microprocessor. Support for this system was added to 4D1-4.x from beginning on (4D1-4.0). Support for Elan, XZ and XS graphics was added shortly thereafter in 4D1-4.0.2. Next support for the new R4000 based model was added in 4D1-4.0.5E.

General support for the Indigo can be found in the all platform releases of IRIX 5.x. Only the R4000 models were supported by IRIX 6.2 and IRIX 6.5. The support for the remaining legacy systems like the Indigo R4000 was dropped after 6.5.22 making IRIX 6.5.22 the last version to support any of these systems.
[[File:Indigo-front-1000.jpg|thumb|IRIS Indigo from the front]]

=== Hardware Problems ===
The Indigo does have a number of potential failures:

==== Battery Failure ====
Signs of failure: The system fails to boot and repeats the message "Can't set tod clock"

This error is very common these days and it occurs during boot time. It usually means that the onboard battery is empty and that the system can't set it's clock. It is not fatal and some systems even recover when they are run for a while. This error does not occur while the system is running.

The original battery used is a Tadiran TL-5186 3.6V battery. Current replacements are the Sonnenschein SL-340 or SL-840. Both can be installed in the same place as the original battery of the Indigo.

In the long run a cheaper solution is to wire a socket for a generic button cell to the battery connectors on the main board. The socket could be fixed on one of the GIO32 bus placeholders. The Indigo will work just fine with a standard and much cheaper 3 V button cell (like a CR2032).

==== Memory Controller ====
Signs of failure: While booting the system displays a message like "Warning: Revision C Memory Controller (MC) chip needed in order to properly operate with SIMMS of this type."

When upgrading memory on an R4000 Indigo IRIX might issue the above warning if there is no Rev C memory controller installed in the system (This can be checked using /usr/gfx/gfxinfo). If all memory is detected (i.e. shown in hinv) and there are not unusual problems with the system since the upgrade it should be safe to ignore the message. It was added when there were bugs in some memory modules. The upgraded Rev C memory controller contains a workaround for these bugs, but as these have also long been fixed there should be no problems today - even with older MCs.

In later IRIX the warning message has been worded differently: "WARNING: You may need a memory controller revision C because of the type of simms installed. If you don't experience any memory errors you won't need MC revision C"

==== Bad eaddr ====
Signs of failure: The system complains about a bad ethernet address (ff:ff:ff:ff:ff:ff).

In general this means that the EEPROM that contains the hardware ethernet address is dead or contains invalid data. It is an 8 pin MiniDIP serial EEPROM (93C56) which is socketed on the backplane.

In many cases the reason is, that in the Indigo different CPU boards (IP20, then IP12) were used. The location of the address is different between the two boards and is properly relocated when a system is upgraded from IP12 to IP20. When the IP12 is placed back in the system the MAC address is erased.

A possible solution is to place the IP12 in the system and reset the mac address from the PROM monitor using the eaddr command - the IP20 doesn't allow that. After that the system can be used with the IP12 board or upgraded to IP20 which will relocate the address once again.

[[Category:Hardware]]</text>
    <sha1>40ca10a8f669b6ed13311554512196948e5c7b2a</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Personal IRIS</title>
  <ns>0</ns>
  <id>18</id>
  <revision>
    <id>313</id>
    <parentid>266</parentid>
    <timestamp>2025-02-23T17:45:37Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4791" xml:space="preserve">The Personal Iris was introduced in 1988 as low end workstation to the IRIS 4D series based on MIPS RISC microprocessors. A model name consists of "4D/" and a code designating the CPU and graphics type. The models replaced the "Twin Tower" style [[Professional IRIS]] series on the low end market, with the [[Power Series]] taking the higher end market. All Personal IRIS systems use a 32-bit MIPS I core and share some parts commonality with the R3000 Indigo in the 30 and 35 models. The last model (4D/35) was introduced in 1991 and presumably sold through 1993 with the release of the Indy heralding the end of the IRIS line.
[[File:PersonalIris.jpg|thumb|A 4D/35 owned by CB_HK of IRIXNet]]

== Models ==
The series came in four models differentiated by badging, and the contents of the system module inside the case. No major external differences are otherwise shown. Between the 4D/2x and the 4D/3x systems are major differences. The latter one uses a totally different system board which besides faster processors includes a newly designed memory interface that allows much higher bandwidth and a larger amount of main memory. The system bus of the newer boards is clocked at 30 MHz instead of 10 MHz.
{| class="wikitable"
|Model
|CPU board
|CPU
|Maximum Memory
|-
|4D/20
|IP6
|MIPS R2000 12.5 MHz
|32MB
|-
|4D/25
|IP10
|MIPS R3000 20 MHz
|32MB
|-
|4D/30
|IP14
|MIPS R3000 30 MHz
|128MB
|-
|4D/35
|IP12
|MIPS R3000 36 MHz
|128MB
|}
The 20 and 25 models use industry standard 30-pin SIMMs. The 30 and 35 models use the same RAM modules as the Indigo R3000.

=== Graphics ===
The Personal IRIS had either a Datastation (Server) configuration, or they could utilize VME-based Eclipse or Express graphics, the latter only being usable on the 30 and 35 models due to a common architecture with the [[IRIS Indigo]]

=== Peripherals ===
The Personal IRIS, unlike later SGIs, does NOT possess support for PS/2 and uses the 4D-style DB9 keyboards used by the Personal/Professional IRIS series. To use PS/2 peripherals necessitates an adapter.

Personal IRIS models 4D/20 and 4D/25 have basic audio capabilities onboard. For audio in 4D/30 and 4D/35 an optional board is required that is plugged into a special slot on the mainboard. That additional board is called Magnum Audio Option and offers 16bit/stereo audio instead of the 8bit/mono audio that was offered on the earlier Personal Iris models.

The Personal IRIS has a built in SCSI controller that supports the internal as well as the external SCSI devices. The SCSI connector is located on the back of machine itself (just right of the E-Module) and is also covered by the plastic skin. The internal drives connect to the same SCSI chain that is also available via that external centronics SCSI port. The SCSI controller is narrow SCSI, Western Digital 33C93A.

All Personal IRIS systems allow the owner to install double height 6U VME devices. The VME interface of the Personal Iris also supports busmaster devices which may directly access the main memory of the computer. Only the 4D/30 and 4D/35 models allow VME block transfer due to a new peripheral controller on the system board.

=== Operating System Support ===
The Personal IRIS line was available during the "IRIX 3.x" era, but more contemporaneously called 4D1-3.x UNIX era. Support continued into IRIX 4.x and 5.x, and was removed along with all other 32-bit options by 5.3.

=== Hardware Problems ===

==== Power Supply ====
Power supply problems are not uncommon with these systems. Unplug the power cord, then open the opposite side of the E-Module and remove the sheetmetal. The power supply has 2 replaceable fuses which are worth to check as well as the proper cabling. One fuse is on the small daughtercard, the other is next to that card and usually covered with a blue plastic cap.

==== Onboard Battery ====
Signs of failure: The system fails to boot and returns to PROM after issuing "Can't set tod clock"

This problem has so far been seen only on the later Personal Iris models (4D/30 and 4D/35). The earlier systems may not be affected and just boot with a faulty date/time.

While there also may be other causes, the by far most likely is an empty battery on the CPU board. The original battery is a 3V coin cell made by Duracell (DL2450). The battery is socketed so replacing it doesn't require any soldering. The cost of the battery is approximately 3 USD / 2 EUR.

==== 4MB Memory Modules ====
Signs of failure: System doesn't work when more than one set of 4MB modules is installed.

This is a known problem and a flaw in the systems hardware of 4D/30 and 4D/35 systems which can not be fixed. The bottom line is, that only one 16MB kit (4x4MB) may be installed - there is no limitation regarding 8MB (4x2MB) or 32MB (4x8MB) kits.
[[Category:Hardware]]</text>
    <sha1>dd757ef0c5ac5b92c5b07e4cb653e6132fd9cc62</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>CD Installation of IRIX</title>
  <ns>0</ns>
  <id>145</id>
  <revision>
    <id>314</id>
    <parentid>297</parentid>
    <timestamp>2025-02-23T18:19:44Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3429" xml:space="preserve">IRIX can be installed via CD starting with IRIX 4.x. However, this guide specifically covers [[IRIX 6.5]]. The reason for this is that pre IRIX 6.5 installation media is often system specific, and no better way of doing it has been found other than referring to official SGI documentation and contacting people who have done it. 

=== Required CDs ===

* IRIX Foundation 1
* IRIX Foundation 2
* IRIX Development Libraries
* IRIX Development Foundation 1.3
* IRIX Overlays (6.5.22 and up have 3 discs)
* IRIX Applications
* IRIX Mipspro Compiler Execution Environment
* IRIX Mipspro C Compiler
* IRIX MIPSPro C++ Compiler
* IRIX ONC3/NFS

This is a bare minimum for a functional install. 

=== Setting up a disklabel ===
Insert the Overlay 1 CD after turning on the SGI and stopping at the Stop for Maintenance screen. Enter the Command Monitor. 

Type &lt;code&gt;hinv&lt;/code&gt; to get a list of SCSI devices. Look for the section labeled SCSI CDROM. The first number is the controller ID, the second the device ID. If it doesn't show up, or multiple show up, then the system has a SCSI misconfiguration. Best course of action is to receive help from the community in that situation. 

Make sure Overlay 1 is inserted. Boot sash (standalone shell):

==== 32-bit SGI ====
&lt;code&gt;boot -f dksc(0,4,8)sashARCS&lt;/code&gt;

&lt;code&gt;boot -f dksc(0,4,7)fx.ARCS --x&lt;/code&gt;

==== 64-bit SGI ====
&lt;code&gt;boot -f dksc(0,4,8)sash64&lt;/code&gt;

&lt;code&gt;boot -f dksc(0,4,7)fx.64 --x&lt;/code&gt;

==== Using fx ====
If done correctly, the output should look like:&lt;pre&gt;
fx version 6.5, Oct  1, 1999
fx: "device-name" = (dksc)
fx: ctlr# = (0)
fx: drive# = (1)
fx: lun# = (0)
...opening dksc(0,1,0)

fx: partitions in use detected on device
fx: devname             seq owner   state
fx: /dev/rdsk/dks0d1s0    1 xfs     already in use

...drive selftest...OK
Scsi drive type == SGI     IBM DDRS-34560W S96A

----- please choose one (? for help, .. to quit this menu)-----
[exi]t             [d]ebug/           [l]abel/           [a]uto
[b]adblock/        [exe]rcise/        [r]epartition/
&lt;/pre&gt;Or otherwise at a prompt. It may require hitting enter a few times or if the system has multiple discs, selecting the proper IDs. 

Type:

&lt;code&gt;repartition&lt;/code&gt;

&lt;code&gt;ro&lt;/code&gt;

&lt;code&gt;../label&lt;/code&gt;

&lt;code&gt;sync&lt;/code&gt;

&lt;code&gt;/exit&lt;/code&gt;

and it should reboot or drop back into PROM. 

=== Install via CD ===
Select Install System Software from the ARCS screen and select CD, follow the instructions. 

After getting in, it should drop into an inst&gt; prompt. Select admin, then mkfs. For a 4G or smaller drive, select 512-byte. For larger, do 4096-byte. 

Next, open each CD in inst. Hit open, then /CDROM/dist. Do this for each CD, swapping them through. 

To setup the install:&lt;pre&gt;
keep *

install standard

keep appletalk kerberos openssl openssh OpenOffice outbox sgi_apache ftn* gsview ghostscript sgitcl_eoe

&lt;/pre&gt;These components are often replaced by FOSS versions under IRIX. 

Then, get ready to swap CDs. Really nothing else to say here. Get ready to stick around for 1-2 hours going CD to CD.

== Reasons to NOT install via CD ==
IRIX CDs are expensive collectors items. IRIX CDs are EFS images and difficult to burn on IRIX. The CD swapping aspect is bad. Anyone with basic UNIX knowledge and networking (and a BSD, Solaris, IRIX or even GNU/Linux box) can do this install faster and easier using any other method. 
[[Category: Tutorials]]
[[Category: No-Images]]</text>
    <sha1>833e41af63d6ea65c782104a572008fffaf56839</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>SGUG RSE</title>
  <ns>0</ns>
  <id>101</id>
  <revision>
    <id>315</id>
    <parentid>206</parentid>
    <timestamp>2025-02-23T19:37:47Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="937" xml:space="preserve">SGUG RSE is a community effort of the Silicon Graphics User Group to develop software for IRIX using a ported version of RPM, along with tdnf and microdnf to provide package management and resolution. It essentially installs itself as a package without any interaction with the larger system. 

==== Toolchain ====
RSE uses GCC 9 which can cross compile with distcc on x86 systems. It uses RPM SPEC files (not to be confused with SGI SPEC files) to generate SRPMs. It is based on Fedora 31. 

==== Packages ====
As of 2025, RSE is still experimental but boasts over 1,000 "packages" of software, of which many are games, media and other software that is of relevance to SGI users.

== Bootstrapping ==
RSE can be installed by doing the following:

Use /usr/sysadm/privbin/modifyUserAccount to add the main user to group sys. 

&lt;code&gt;systune ncargs 262144&lt;/code&gt;
[[Category:Open-Source-Software]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>0e48c0d889461cf234b67a9e2f1423b636f647ef</sha1>
  </revision>
  <revision>
    <id>316</id>
    <parentid>315</parentid>
    <timestamp>2025-02-23T19:40:50Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1123" xml:space="preserve">SGUG RSE is a community effort of the Silicon Graphics User Group to develop software for IRIX using a ported version of RPM, along with tdnf and microdnf to provide package management and resolution. It essentially installs itself as a package without any interaction with the larger system. 

==== Toolchain ====
RSE uses GCC 9 which can cross compile with distcc on x86 systems. It uses RPM SPEC files (not to be confused with SGI SPEC files) to generate SRPMs. It is based on Fedora 31. 

==== Packages ====
As of 2025, RSE is still experimental but boasts over 1,000 "packages" of software, of which many are games, media and other software that is of relevance to SGI users.

== Bootstrapping ==
RSE can be installed by doing the following:

Use /usr/sysadm/privbin/modifyUserAccount to add the main user to group sys. 

&lt;code&gt;systune ncargs 262144&lt;/code&gt;

Download the RSE archives from [https://github.com/sgidevnet/sgug-rse/releases GitHub]

There are always three. 

Extract the archives as root to /usr. 

Use tdnf to search the repos. 
[[Category:Open-Source-Software]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>7aaf6c8971c4276f96178258ae3098012ac550dc</sha1>
  </revision>
  <revision>
    <id>317</id>
    <parentid>316</parentid>
    <timestamp>2025-02-23T19:41:12Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1127" xml:space="preserve">SGUG RSE is a community effort of the Silicon Graphics User Group to develop software for IRIX using a ported version of RPM, along with tdnf and microdnf to provide package management and resolution. It essentially installs itself as a package without any interaction with the larger system. 

==== Toolchain ====
RSE uses [[GCC]] 9 which can cross compile with distcc on x86 systems. It uses RPM SPEC files (not to be confused with SGI SPEC files) to generate SRPMs. It is based on Fedora 31. 

==== Packages ====
As of 2025, RSE is still experimental but boasts over 1,000 "packages" of software, of which many are games, media and other software that is of relevance to SGI users.

== Bootstrapping ==
RSE can be installed by doing the following:

Use /usr/sysadm/privbin/modifyUserAccount to add the main user to group sys. 

&lt;code&gt;systune ncargs 262144&lt;/code&gt;

Download the RSE archives from [https://github.com/sgidevnet/sgug-rse/releases GitHub]

There are always three. 

Extract the archives as root to /usr. 

Use tdnf to search the repos. 
[[Category:Open-Source-Software]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>c484e7c29bb84553c1502045b0d36d4d74cfb829</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Itanium</title>
  <ns>0</ns>
  <id>109</id>
  <revision>
    <id>318</id>
    <parentid>287</parentid>
    <timestamp>2025-02-23T19:53:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3255" xml:space="preserve">[[File:Intel Itanium Logo.png|thumb|Explicitly parallel instruction computing]]
Itanium, also known as IA-64 and IPF (Itanium Processor Family), is a RISC-like CPU architecture developed by HPE and Intel in the 1990s to serve as a high end, 64-bit, RISC processor architecture to replace HP's PA-RISC. Incidentally, SGI also adopted it to replace [[MIPS]] due to being unable to continue MIPS development due to early 2000s financial difficulties. 

== History of Itanium ==
In 1989 the Fort Collins Design Center, a part of Hewlett Packard, but now a part of Intel, began work on a new RISC architecture to exceed the performance of current RISC iterations. Intel joined the alliance in 1994 and quickly became the face of Itanium. 

Due to delays and development hell, the 1997-1998 launch window was missed and Merced, the initial Itanium design, only began shipping volume around 2001. At that time, Merced was neither competitive or impressive. This, combined with continued delays of Itanium 2, negative press from consumer publications misunderstanding Itanium's purpose (It was never designed to replace x86) and mismanagement led many partners to evacuate the Itanium alliance. 

By 2005, IBM, Sun, Dell and many others had mostly evacuated the Itanium alliance, leaving HP and several Japanese companies (e.g. Hitachi) as Intel's primary customer. SGI shipped Itanium, but not in sufficient volume, and by 2008 SGI declared bankruptcy. 

In 2017, a higher stepping of Poulson, called Kittson, shipped and was the last Itanium processor type. All units were shipped by mid-2019.  

== Design ==
Itanium uses the EPIC (Explicitly Parallel Instruction Computing), but internally it resembles the Berkeley RISC design, with register windowing, in-order opcode loading, mostly fixed length instructions, etc. It differs from traditional RISC in using VLIW-like instruction bundling to enable parallel execution. It additionally had 64-bit SIMD instructions, similar to MMX.

== Performance ==
Itanium was smashed by public consumer media due to dishonest benchmarking (x86 emulation mode used for benchmarking, and other dishonest claims) and seen as a poor replacement for x86, which it was never designed to do. It often led during the mid-2000s on [https://www.spec.org/cpu2006/results/res2009q2/cpu2006-20090522-07485.html floating point and integer workloads] and was never intended as a general purpose CPU. Itanium's performance is often tied to the compiler used, with Open64 and GCC doing quite poorly compared to HP's aCC and Intel's C++ compiler. 

== In SGIs ==
On the collector market, the Prism is often considered desirable, but all other SGI Itanium systems have never had the same cult following. This is due to a combination of factors:

* IRIX users do not find GNU/Linux particularly enticing. 
* The systems only run Windows for Itanium and GNU/Linux itanium distributions. 

As a result, most Altices can be had at bargain bin prices. 

== Market Performance ==
Itanium shipped more than 4 billion units during its lifetime, the lion's share under HPE, with the remainder primarily under the Japanese market. By the time of Poulson and Kittson, however, it had very few new customers. 
[[Category:Stubs]]
[[Category:Processors]]</text>
    <sha1>3e1da32426e7ee50d59989e9abed5e8b0b8703d0</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>QIC</title>
  <ns>0</ns>
  <id>146</id>
  <revision>
    <id>319</id>
    <timestamp>2025-02-23T19:59:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "'''QIC''', meaning Quarter Inch Cartridge, is a tape format used to distribute [[GL2-3.x|GL2]] and [[4D1-3.x|4D1]] prior to the introduction of CDs with [[IRIX 4.0]] and later."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="176" xml:space="preserve">'''QIC''', meaning Quarter Inch Cartridge, is a tape format used to distribute [[GL2-3.x|GL2]] and [[4D1-3.x|4D1]] prior to the introduction of CDs with [[IRIX 4.0]] and later.</text>
    <sha1>c81cb40064ac453537109a48b324ec84d9dbe854</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Professional IRIS</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>320</id>
    <parentid>141</parentid>
    <timestamp>2025-02-24T02:00:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1954" xml:space="preserve">The first widely produced MIPS powered SGIs, these systems were historically called the IRIS 4D GT series. Commonly called the "Twin Towers" due to the distinctive look caused by the disks being kept in a smaller sidecar tower, these systems are notable for being among the most rare and undocumented MIPS powered SGIs. Released firstly as the 4D/60, then as three models, the high end 4D/80, the midrange 4D/70 and the low end 4D/50 differing by CPU and graphics configuration, and the ultimate 4D/85 released in late 1988. The "Twin Towers" design seems to have carried over into the early POWERSeries systems released much later.
[[File:4D50GT.jpg|thumb]]

== Hardware ==
The unusual Twin Tower design is the result of engineering decisions that led to the smaller tower containing the disk array of the system, with the larger tower containing the graphics boards. This concept of two asymmetrical towers is distinctive and appears unreplicated by anyone but SGI.

The heart of each system is a MIPS R2000 MIPS I 32-bit RISC CPU, replacing the earlier IRIS 2000 and 3000 model line powered by the Motorola 68000 line. Each system's CPU board could hold a maximum of 16MB RAM, with the 4D/80 allowing an additional set of boards totaling 144MB.

The Clover 1 and 2 systems, called G and GT respectively (for Graphics, and Graphics, Textured presumably) were the primary graphics options of the systems.

Similar to other IRIS4D machines, they used a DB9 custom serial keyboard and mouse, similar to the Personal IRIS.

Some reports point to a 4D/85 Single tower model being offered, but little to nothing is known about it.
[[File:Prime-IRIS.jpg|left|frame]]

=== Operating System Support ===
The Personal IRIS line was available during the "IRIX 3.x" era, but more contemporaneously called 4D1-3.x UNIX era. Support continued into IRIX 4.x and 5.x, and was removed along with all other 32-bit options by 5.3.

[[Category:Hardware]]
[[Category:Stubs]]</text>
    <sha1>f05450354993769cef95ce822b8d350e6a227b41</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>IRIXNet</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>321</id>
    <parentid>257</parentid>
    <timestamp>2025-02-24T02:02:12Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1239" xml:space="preserve">[[File:Irixnet mainpage.jpg|thumb|Main page of IRIXNet, captured Feb 2025]]
IRIXNet, short for IRIX Network, is a Silicon Graphics-focused website, forum and archive of former hobbyist sites that was founded in 2017 by Raion (Kaz Kuroi) and Praetor (George). It was founded with the express purpose of providing a secondary Silicon Graphics site separate to [[Nekochan.net]] due to recent concerns of downtime at the time, and to facilitate open sales of commercial software. 

== Contents ==
IRIXNet has an archive, file servers, gallery and forums. It exists as one of two English language SGI-related sites offering forums, the other being [[SGUG]].

=== History ===
IRIXNet was founded in 2017 to serve as a feeder site for Nekochan.net. However on May 21, 2018 Nekochan went offline for the final time and IRIXNet was pushed into a role of being the primary community. [[SGUG]] was founded a year later in 2019 for the same purpose. 

=== Association with TechPubs ===
TechPubs is owned by Raion, who also owns IRIXNet, but the purpose of Techpubs is far more focused on documentation and to serve as an SEO-friendly SGI instructional website. It does not inherit the moderation team or policies of IRIXNet.


[[Category:Communities]]</text>
    <sha1>334889c01f5b61b0d36cfe4038b717f28a9565db</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Flexlm License</title>
  <ns>0</ns>
  <id>147</id>
  <revision>
    <id>322</id>
    <timestamp>2025-02-24T02:18:21Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "This is a haxforce [[Flexlm]] License file. Use at your own risk.   #  # FLEXlm license file  #  ## FLEXlm License File FLMLF 1.0  ## Filename:/var/flexlm/license.dat    FEATURE TV/Base toolworks 3.800 1-jan-0 0 1C466A88CDF55FAD72F6 HOSTID=ANY \           ISSUER="Hax Force, Inc."  FEATURE TV/AnyChip-AnyOS toolworks 3.800 1-jan-0 0 ACB60AF81EC176CB3072 \           HOSTID=ANY ISSUER="Hax Force, Inc."  FEATURE TV/AnyChip-AnyOS/MP/Big toolworks 3.800 1-jan-0 0 3C36AA98536D92..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7856" xml:space="preserve">This is a haxforce [[Flexlm]] License file. Use at your own risk. 
 #
 # FLEXlm license file
 #
 ## FLEXlm License File FLMLF 1.0
 ## Filename:/var/flexlm/license.dat
 
 FEATURE TV/Base toolworks 3.800 1-jan-0 0 1C466A88CDF55FAD72F6 HOSTID=ANY \
          ISSUER="Hax Force, Inc."
 FEATURE TV/AnyChip-AnyOS toolworks 3.800 1-jan-0 0 ACB60AF81EC176CB3072 \
          HOSTID=ANY ISSUER="Hax Force, Inc."
 FEATURE TV/AnyChip-AnyOS/MP/Big toolworks 3.800 1-jan-0 0 3C36AA98536D925B25EC \
          HOSTID=ANY ISSUER="Hax Force, Inc."
 FEATURE TV/AnyChip-AnyOS/PE toolworks 3.800 1-jan-0 0 5CA6CA78FC82CD639C59 \
          HOSTID=ANY ISSUER="Hax Force, Inc."
 FEATURE TV/AnyChip-AnyOS/PGIHPF toolworks 3.800 1-jan-0 0 ECC69A588D7C1EC842FA \
          HOSTID=ANY ISSUER="Hax Force, Inc."
 FEATURE MPEG_Encoder sgifd 1.000 1-jan-0 0 FC06EA34D1949044BC74 HOSTID=ANY \
          vendor_info="MPEG ENCODER" ISSUER="Hax Force, Inc."
 FEATURE CINEPAK_Encoder sgifd 1.000 1-jan-0 0 EC56AA04E319E54BF986 \
          HOSTID=ANY vendor_info="CINEPAK ENCODER" ISSUER="Hax Force, Inc."
 
 FEATURE cosmoworlds sgifd 1.000 1-jan-0 0 3C864A245335146AE7E9 HOSTID=ANY \
          vendor_info="COSMO WORLDS" ISSUER="Hax Force, Inc."
 
 FEATURE CosmoCode sgifd 2.000 1-jan-0 0 FCF66A54DDE13FDB4FDB HOSTID=ANY \
          vendor_info="COSMO CODE" ISSUER="Hax Force, Inc."
 
 FEATURE cpp sgifd 7.000 1-jan-0 0 8CE65AB48DDCD394E6E1 HOSTID=ANY \
          vendor_info="C++ &lt;=128 CPU" ISSUER="Hax Force, Inc."
 
 FEATURE cc sgifd 7.000 1-jan-0 0 ACE61A24A73E99462ECC HOSTID=ANY \
          vendor_info="C &lt;=128 CPU" ISSUER="Hax Force, Inc."
 
 FEATURE auto_pp sgifd 7.000 1-jan-0 0 8C862A14661D81BA12EB HOSTID=ANY \
          vendor_info="APO &lt;=128 CPU" ISSUER="Hax Force, Inc."
 
 FEATURE pcpcol sgifd 1.000 1-jan-0 0 2C160AA4D66A13FE9B31 HOSTID=ANY \
          vendor_info="PCP COLLECTOR" ISSUER="Hax Force, Inc."
 
 FEATURE pcpmon sgifd 1.000 1-jan-0 0 7CD6BA645E2207A47581 HOSTID=ANY \
          vendor_info="PCP MONITOR" ISSUER="Hax Force, Inc."
 
 FEATURE netvisualizer sgifd 2.000 1-jan-0 0 6C566A94B429608FA8DE HOSTID=ANY \
          vendor_info="NET DISPLY STN" ISSUER="Hax Force, Inc."
 PACKAGE MayaCDS sgiawd 1.500 90B090A1BF3C146C7AFC \
          COMPONENTS="Maya:1.5:1 MayaFX:1.5:1 MayaArtisan:1.5:1" \
          OPTIONS=SUITE
 FEATURE Maya sgiawd 1.500 1-jan-0 0 2CA6BAC4F3A1E748824F HOSTID=ANY \
          ISSUER="Hax Force Inc."
 FEATURE Mayaf sgiawd 1.500 1-jan-0 0 2CA66A045CFD0D12C27E HOSTID=ANY \
          ISSUER="Hax Force Inc."
 FEATURE MayaUpdate sgiawd 1.500 1-jan-0 0 1CB6DA74841741540791
 HOSTID=ANY \
          ISSUER="Hax Force Inc."
 FEATURE MayaFX sgiawd 1.500 1-jan-0 0 9C866A14954436B78283 HOSTID=ANY \
          ISSUER="Hax Force Inc."
 FEATURE MayaVFX sgiawd 1.500 1-jan-0 0 3C464AE43029A927CEBD HOSTID=ANY \
          ISSUER="Hax Force Inc."
 FEATURE MayaFXf sgiawd 1.500 1-jan-0 0 9C466A242075DF63CEC3 HOSTID=ANY \
          ISSUER="Hax Force Inc."
 
 FEATURE MayaCDS sgiawd 1.500 1-jan-0 0 AC96BA645F0E1391B9B3 HOSTID=ANY \
          ISSUER="Hax Force Inc."
 FEATURE AW_VP sgiawd 3.200 1-jan-0 0 DC462A84CF2755BD0650 HOSTID=ANY \
          ISSUER="Hax Force Inc."
 FEATURE AW_UTIL sgiawd 1.000 1-jan-0 0 0C366AA46CB6B52FCE2D HOSTID=ANY \
          ISSUER="Hax Force Inc."
 PACKAGE MayaUnlimited sgiawd 1.500 A0B00041AEA500E897B3 \
          COMPONENTS="MayaLive:1.0:1 MayaCloth:1.0:1 MayaFur:1.0:1" \
          OPTIONS=SUITE
 FEATURE MayaUnlimited sgiawd 1.500 1-jan-0 0 1C464AE4CAF95E7038DF \
          HOSTID=ANY ISSUER="Hax Force Inc."
 PACKAGE MayaUnlimitedV sgiawd 1.500 00C000B13C5377DD97B1 \
          COMPONENTS=MayaFurV:1.0:1 OPTIONS=SUITE
 FEATURE MayaUnlimitedV sgiawd 1.500 1-jan-0 0 1C86EA14550E27EDB606 \
          HOSTID=ANY ISSUER="Hax Force Inc."
 PACKAGE MayaCDSV sgiawd 1.500 40903071139CC1EAC153 \
          COMPONENTS="MayaV:1.5:1 MayaVFX:1.5:1" OPTIONS=SUITE
 FEATURE MayaCDSV sgiawd 1.500 1-jan-0 0 ACC62A9492820A092C80 HOSTID=ANY \
          ISSUER="Hax Force Inc."
 FEATURE AW_MPM sgiawd 1.500 1-jan-0 0 6C66CAF45E76FA454397 HOSTID=ANY \
          ISSUER="Hax Force Inc."
 FEATURE cosmocreate sgifd 1.000 1-jan-0 0 0C568A9467B3290A3A6F HOSTID=ANY \
          vendor_info=COSMOCREATE ISSUER="Hax Force, Inc." ck=23
 FEATURE CosmoCode sgifd 2.000 1-jan-0 0 FCF66A54DDE13FDB4FDB HOSTID=ANY \
          vendor_info="COSMO CODE" ISSUER="Hax Force, Inc." ck=119
 FEATURE cosmoworlds sgifd 1.000 1-jan-0 0 3C864A245335146AE7E9 HOSTID=ANY \
          vendor_info="COSMO WORLDS" ISSUER="Hax Force, Inc." ck=248
 FEATURE mediaserver sgifd 3.000 1-jan-0 0 ACE65AC4B75C79361600 \
          VENDOR_STRING=ANY HOSTID=ANY vendor_info="Media Base ANY" \
          ISSUER="Hax Force, Inc." ck=26 SN=234050
 FEATURE mediaserver sgifd 1.000 1-jan-0 0 4CE6AA442DC5102ED5F9 \
          VENDOR_STRING=S,DM,L,XL HOSTID=ANY vendor_info="MEDIABASE XL" \
          ISSUER="Hax Force, Inc." ck=35
 FEATURE MineSet_client sgifd 2.500 1-jan-0 0 ECA6FA64807D0E89B52B \
          HOSTID=ANY vendor_info="MINESET CLIENT" ISSUER="Hax Force, Inc." \
          ck=134 SN=234057
 FEATURE MineSet_server sgifd 2.500 1-jan-0 0 5C669A9414032A215332 \
          HOSTID=ANY vendor_info="MINESET SERVER" ISSUER="Hax Force, Inc." \
          ck=135 SN=234100
 FEATURE MineSet_server sgifd 2.500 1-jan-0 0 2C666A841C486F95DDB5 \
          VENDOR_STRING=5up HOSTID=ANY vendor_info="MINESET SERVER" \
          ISSUER="Hax Force, Inc." ck=243 SN=234103
 FEATURE f90 sgifd 7.000 1-jan-0 0 4C66BA143C7230ED9230 HOSTID=ANY \
          vendor_info="F90 &lt;=128 CPU" ISSUER="Hax Force, Inc." ck=42
 FEATURE f77 sgifd 7.000 1-jan-0 0 ACC63A346C444B7C99A7 HOSTID=ANY \
          vendor_info="F77 &lt;=128 CPU" ISSUER="Hax Force, Inc." ck=0
 FEATURE auto_pp sgifd 7.000 1-jan-0 0 8C862A14661D81BA12EB HOSTID=ANY \
          vendor_info="APO &lt;=128 CPU" ISSUER="Hax Force, Inc." ck=26
 FEATURE netvisualizer sgifd 2.000 1-jan-0 0 6C566A94B429608FA8DE HOSTID=ANY \
          vendor_info="NET DISPLY STN" ISSUER="Hax Force, Inc." ck=38
 FEATURE netvis_datastation sgifd 2.000 1-jan-0 0 3CC65A04E920B402F84B \
          HOSTID=ANY vendor_info="NETV DATA STN" ISSUER="Hax Force, Inc." \
          ck=216
 FEATURE normalizer sgifd 1.000 1-jan-0 0 DC968AE44FFB1573E7C8 HOSTID=ANY \
          vendor_info=normalizer ISSUER="Hax Force, Inc." ck=48
 FEATURE WorkShop sgifd 2.000 1-jan-0 0 6C16DAD49AC3AF2388D3 HOSTID=ANY \
          vendor_info="PRODEV WORKSHOP" ISSUER="Hax Force, Inc." ck=73
 FEATURE WorkShopMPF sgifd 2.000 1-jan-0 0 BCF69A24F40E9748B2A2 HOSTID=ANY \
          vendor_info="WORKSHOP PRO MPF" ISSUER="Hax Force, Inc." ck=83
 FEATURE propel sgifd 2.000 1-jan-0 0 1CC68A84F4DDE1C2776D HOSTID=ANY \
          vendor_info=Propel ISSUER="Hax Force, Inc." ck=86
 FEATURE provision sgifd 1.000 1-jan-0 0 5C869AA411A952448575 HOSTID=ANY \
          vendor_info=Provision ISSUER="Hax Force, Inc." ck=222
 FEATURE RapidApp sgifd 1.000 1-jan-0 0 7C963AA48668A9763CEE HOSTID=ANY \
          vendor_info=RAPIDAPP ISSUER="Hax Force, Inc." ck=54
 FEATURE wf_director sgifd 2.000 1-jan-0 0 DCB61A74211D71B5845A \
          VENDOR_STRING=WFD HOSTID=ANY vendor_info="WF Director" \
          ISSUER="Hax Force, Inc." ck=233 SN=234155
 FEATURE cpp sgifd 7.000 1-jan-0 0 8CE65AB48DDCD394E6E1 HOSTID=ANY \
          vendor_info="C++ &lt;=128 CPU" ISSUER="Hax Force, Inc."
 FEATURE Insignia_SoftWindows95 insignia 4.000 01-jan-0 0 \
         ECE41259D5BE4700DC27 VENDOR_STRING="5100 0100 0000 0001" \
         HOSTID=ANY vendor_info=SOFTWINDOWS95 ISSUER="Silicon Graphics, \
         Inc."
 FEATURE MPEG_Encoder sgifd 1.000 01-jan-0 0 5CC152087FDCAEDEA1AC \
         HOSTID=ANY vendor_info="MPEG ENCODER" ISSUER="Silicon Graphics, Inc."
 FEATURE CINEPAK_Encoder sgifd 1.000 01-jan-0 0 3CD11288C0DE3AA0FB5C \
         HOSTID=ANY vendor_info="CINEPAK ENCODER" ISSUER="Silicon Graphics,\
         Inc."</text>
    <sha1>b09a3811ccd63b7f0d2578ffab1bee71e38b037e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Flexlm</title>
  <ns>0</ns>
  <id>148</id>
  <revision>
    <id>323</id>
    <timestamp>2025-02-24T02:20:44Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Flexlm is a license management software for IRIX included with every installation and used for things like MIPSPro and ProDev Workshop tools.  Due to the age, Flexlm is unmaintained on IRIX and considered abandonware. A license is below.  [[Flexlm License]]  [[Category:Stubs]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="277" xml:space="preserve">Flexlm is a license management software for IRIX included with every installation and used for things like MIPSPro and ProDev Workshop tools.

Due to the age, Flexlm is unmaintained on IRIX and considered abandonware. A license is below.

[[Flexlm License]]

[[Category:Stubs]]</text>
    <sha1>4f5c5630434f40695c8431ef6cfc4e38564425d6</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Network Setup</title>
  <ns>0</ns>
  <id>10</id>
  <revision>
    <id>324</id>
    <parentid>14</parentid>
    <timestamp>2025-02-24T04:33:41Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Major Components */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3949" xml:space="preserve">IRIX unlike modern Linux distros, Windows and macOS necessitates some level of manual configuration.

Some of the tasks here can be accomplished via the GUI, but it is valuable to understand the networking stack in IRIX.

This guide applies to [[IRIX 6.5]] in particular. 

=== Major Components ===
IRIX's network stack consists of several components:

* inetd - This not only controls the major network services, like telnet and rlogind, it also controls the network and updates to the network necessitate restarts of inetd.
* /etc/hosts - The hosts file, which sets the IP address of the server.
* /etc/nsswitch.conf - This tells IRIX where to obtain various components.
* /etc/resolv.conf - This contains the resolvers IRIX uses, plus the search domain.
* /etc/sys_id - Sets the hostname.
* /etc/config/static-route.options - Sets the default routes in absence of DHCP.
* /etc/config/ipaliases.options - For additional IP addresses.
* routed - Used for DHCP routing.
* autoconfig_ipaddress - DHCP service

With some luck IRIX DHCP will work out of the box, but it's good practice to set static network IPs for management purposes.

=== Static IP Setup ===
What follows is a guide intended to provide a basic set up into setting up network on IRIX 6.5 or later. For older versions, please check Apocrypha

Set the Hostname:

&lt;code&gt;# printf "octane" &gt; /etc/sys_id&lt;/code&gt;

The above command will set the hostname to octane. Set it as desired by replacing the string inside the quotes. This does NOT include the domain name.

==== Assign IP Address ====
To self-assign an IP, open up the /etc/hosts file and remove the IRIS line. Then, add the following line:

&lt;code&gt;192.168.1.10 octane.home.local octane&lt;/code&gt;

This line should be the desired IP, followed by the fully qualified hostname, and the hostname at the end.

==== Turning off DHCP and routed ====
Now, disable these:&lt;pre&gt;
# chkconfig autoconfig_ipaddress off

# chkconfig routed off
&lt;/pre&gt;

==== IP Aliasing ====
This step is optional, but if more IP addresses are required, they can be added.

First, verify the default interface:&lt;pre&gt;
% /usr/etc/ifconfig -a

tg0: flags=8f15c43&lt;UP,BROADCAST,RUNNING,FILTMULTI,MULTICAST,CKSUM,DRVRLOCK,LINK0,L2IPFRAG,L2TCPSEG,IPALIAS,HIGHBW,IPV6&gt;

inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255

lo0: flags=8001849&lt;UP,LOOPBACK,RUNNING,MULTICAST,CKSUM,IPV6&gt;

inet 127.0.0.1 netmask 0xff000000
&lt;/pre&gt;lo0 is the localhost loopback, so the default will generally be the other interface, unless there's many cards, in which case, it's a matter of trial and error if not known.

In any case, once determined, move on to setting aliases. Edit &lt;code&gt;/etc/config/ipaliases.options&lt;/code&gt;, adding aliases using the following syntax:

&lt;code&gt;tg0 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255&lt;/code&gt;

Now turn on the service:

&lt;code&gt;# chkconfig ipaliases on&lt;/code&gt;

==== DNS ====
Next, edit /etc/resolv.conf with DNS servers and search domains:

nameserver 208.67.222.222 # This is OpenDNS

nameserver 1.1.1.1 # This is Cloudflare, also recommended

domain home.local

To ensure that this file is correctly permissioned, run:

&lt;code&gt;# chmod 644 /etc/resolv.conf&lt;/code&gt;

==== nsswitch.conf ====
This step ensures that rogue NIS/yp services don't interfere. If planning to use NIS/yp, skip this step.

Change the hosts line to read: "hosts: files dns"

==== Routing ====
Finally, add a static route to the default gateway in &lt;code&gt;/etc/config/static-route.options&lt;/code&gt;. It is necessary to know this for this guide to work.

&lt;code&gt;$ROUTE $QUIET add net default 192.168.1.1&lt;/code&gt;

Reboot and the network should start working.

=== IPv6 ===
IRIX includes support for IPv6 and it can be enabled as follows:

First, tune the kernel:

&lt;code&gt;systune ip6_enable 1&lt;/code&gt;

Then reboot.

Due to some bugs, it's necessary to check strings in the ipv6 files:

&lt;nowiki&gt;#&lt;/nowiki&gt; strings /var/ns/lib/libns_dns.so | grep ip6&lt;pre&gt;
ip6.arpa.

ip6_rtld
&lt;/pre&gt;</text>
    <sha1>2cfee56907bb15d3c61a64de31eb785f0c31746b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>IRIX Setup 101</title>
  <ns>0</ns>
  <id>7</id>
  <revision>
    <id>325</id>
    <parentid>170</parentid>
    <timestamp>2025-02-24T04:35:53Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Network Setup */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12473" xml:space="preserve">For newcomers to IRIX, setting up IRIX for the first time can be daunting. This aims to break it down into selective, easy-to-follow sections for a post-install IRIX.

=== Forenotes ===
Due to specificity of various hardware and IRIX versions, this guide primarily assumes IRIX 6.5.21+ and that the user is interested in running Nekoware, optxeno, or another product offered on IRIXNet. It is advised to go into this understanding what the goals of the user are exactly.

Per the Style Guide all root commands will be prefixed with #, all user-level commands will be prefixed with % (for the tcsh shell).

=== First Steps ===

==== Securing root ====
Either login on the login screen to root, or serial in via root. Open a terminal window by clicking Desktop - &gt; Open Unix Shell. This is the root shell of the account, and for clarity sake, most commands will be performed via terminal. Type &lt;code&gt;# passwd&lt;/code&gt; and set a secure password for the root user. If doing this from GUI (i.e. EZSetup, this will cover most of the important settings covered there) be warned IRIX will not accept passwords greater than 8 chars in length. From the commandline, there is no such limitations.

==== Network Setup ====
A detailed article can be found at [[Network Setup]].

==== Date and Time ====
Again, a detailed article can be found at [[Keeping Time]].

==== Move $HOME for root ====
Now it is necessary to make a space for root. Due to IRIX's default install, root's home directory is effectively /, the root of the filesystem. '''This is bad. Do not skip this step.'''

Home directories are defined in &lt;code&gt;/etc/passwd&lt;/code&gt;. First, make the directory: &lt;code&gt;# mkdir /root; chmod go-wrx /root&lt;/code&gt; And then update the root line to look like so: &lt;code&gt;root::0:0:Super-User:/root:/bin/tcsh&lt;/code&gt; This can be automated (carefully) with a perl, awk, or sed command, but be careful.

Now clean up: &lt;code&gt;# cd /; rm -rf Desktop dumpster .Sgiresources .cshrc .login .profile .varupdate .wshttymode .desktop-IRIS .desktophost&lt;/code&gt;

Log out and log back in again.

=== Securing IRIX ===

==== Lock unsafe accounts ====
IRIX by default is installed with several accounts without passwords. Checking this is easy: &lt;code&gt;# passwd -as&lt;/code&gt;

Locking the accounts on a normal IRIX install is easy:

&lt;code&gt;# foreach account (lp EZsetup nuucp demos guest OutOfBox sys adm sysadm cmwlogin auditor dbadmin sgiweb 4Dgifts); passwd -l $account; end&lt;/code&gt;

==== Creating a user account ====
Next, create a user account for normal usage, as running as root 24/7 is dangerous. It's easily and safely done using tools in the privbin: &lt;code&gt;# /usr/sysadm/privbin/addUserAccount -l username -S `which tcsh` -H /usr/people/username -C -u 1034 -g 20&lt;/code&gt;

The above example will create a user called '''username''' with a default shell of tcsh, a home directory of &lt;code&gt;/usr/people/username&lt;/code&gt; (/home is NOT a thing on IRIX), create the directory (-C flag) with a uid of 1034 and membership in the user group (ID 20). It may also be advisable to create a group with the same username created by the command above, however that requires manually adding a group to &lt;code&gt;/etc/group&lt;/code&gt; and editing permissions on the home directory. This may be covered in a future installment.

==== Enable Shadow Passwords ====
By default IRIX uses crypt() hashes in /etc/passwd

This is now discouraged and insecure, so it is preferred to enable /etc/shadow. Run &lt;code&gt;pwconv&lt;/code&gt; to enable it.

==== Edit system defaults ====
The file &lt;code&gt;/etc/default/login&lt;/code&gt; controls primary login behavior. Edit the files options to look something akin to this:&lt;pre&gt;
CONSOLE=/dev/console

PASSREQ=YES

ALTSHELL=YES

MANDPASS=YES

UMASK=027

TIMEOUT=60

DISABLETIME=300

MAXTRYS=3

LOGFAILURES=4

IDLEWEEKS=2

PATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11:

SUPATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/etc:/usr/etc:/usr/bin/X11:

SYSLOG=ALL

INITGROUPS=YES

LANG=C

SVR4_SIGNALS=NO

LOCKOUT=4

LOCKOUTEXEMPT=root
&lt;/pre&gt;Note that it is a good opportunity to add extra pathnames that all users will have in PATH. Examples include /usr/nekoware/bin, /opt/xeno/bin, et cetera.

chmod the file to 444 next: &lt;code&gt;# chmod 444 /etc/default/login&lt;/code&gt;

==== File Alteration Monitor ====
For security reasons, edit &lt;code&gt;/etc/fam.conf&lt;/code&gt; to have local_only = true instead of local_only = false.

==== Disable Vulnerable Network Services ====
The following network services are wholly unnecessary for most installations and can be disabled with the following command string:&lt;pre&gt;
# chkconfig sgi_apache off; chkconfig webface_apache off; chkconfig appletalk off; \

chkconfig timed off; chkconfig timeslave off; chkconfig esp off; chkconfig ipaliases off; \

chkconfig ypmaster off; chkconfig yp off; chkconfig sendmail off; chkconfig sendmail_cf off; \

chkconfig webface off; chkconfig named off; chkconfig rsvpd off; chkconfig privileges off
&lt;/pre&gt;Additionally, disabling the following services in &lt;code&gt;/etc/inetd.conf&lt;/code&gt; is prudent, except telnet if an ssh server isn't installed yet, and the system is a server. If that's the case, hold off on that one:&lt;pre&gt;
finger

bootp

tftp

echo

telnet

ftp

discard

chargen

daytime

time

rstatd

walld

rusersd

rquotad

sprayd

ttdbserverd

shell

exec

http

wn-http

ntalk

mountd

sgi_mountd

rexd

bootparam

ypupdated

sgi_videod

sgi_toolkitbus

sgi_snoopd

sgi_pcsd

sgi_pod

sgi_espd

sgi-esphttp

tcpmux/sgi_scanner
&lt;/pre&gt;Some of the above can be re-enabled depending on what is necessary, but the esp ones should not be re-enabled.

==== Secure the X server ====
Edit &lt;code&gt;/var/X11/xdm/xdm-config&lt;/code&gt; and change the DisplayManager*authorize line to read: &lt;code&gt;DisplayManager*authorize: on&lt;/code&gt;

==== Tune the kernel for security ====
Changing these if they are not in use is prudent:&lt;pre&gt;
# printf 'y' | systune ipforwarding 0

# printf 'y' | systune ip6forwarding 0

# printf 'y' | systune icmp_dropredirects 1

# printf 'y' | systune tcp_2msl 60

# printf 'y' | systune allow_brdaddr_srcaddr 0

# printf 'y' | systune tcpiss_md5 1

# printf 'y' | systune restricted_chown 1

# printf 'y' | systune ncargs 131072

&lt;/pre&gt;run &lt;code&gt;# /etc/autoconfig -vf&lt;/code&gt; to rebuild the kernel, and then reboot for full changes to take effect.

==== Install Patches ====
A collection of patches obtained from user backups of sgi.com's support centre is here: &lt;nowiki&gt;http://ftp.irixnet.org/sgi-irix/patches/&lt;/nowiki&gt;

Install all patches for the IRIX version being ran. (inst will not install irrelevant patches on the system).

=== Customizing IRIX ===
Now that security is improved, the actual fun can begin to customizing the IRIX experience.

==== Setup flexlm ====
Place licenses for products in /var/flexlm/license.dat. Softwindows and a few others use different locations. There is a license file in the wiki as well. (search for it!)

==== Enable 24 bit X ====
Unless the graphics in the system are 8-bit (such as an Indy with an XL/8 card), enabling Truecolor will improve the user experience. Edit &lt;code&gt;/var/X11/xdm/Xservers&lt;/code&gt; to be &lt;code&gt;:0 secure /usr/bin/X11/X -bs -nobitscale -c -class TrueColor -depth 24 -solidroot sgilightblue -cursorFG red -cursorBG white&lt;/code&gt;

==== Enable scrollwheel. ====
IRIX by default can't use a scroll wheel. This can be rectified in the kernel:

&lt;code&gt;# systune pcmouse_mode 2&lt;/code&gt;

This sets the scroll wheel to work as on a PC. Mode 3 will set any additional buttons on the mouse to scroll. (it only detects 2 extra buttons)

==== Reduce gamma ====
Set gamma with the following command as root: &lt;code&gt;gamma 1.2&lt;/code&gt; or another value. This will lower the default to a more natural level.

==== Custom tcsh prompt ====
tcsh is a fast, simple UNIX shell that supports most of the same features as bash from an interactive standpoint, and is faster at startup.

Here is a configuration file for root:&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${red}%n${blue}@%m ${yellow}%~ ${red}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;


This sets a red prompt as a reminder. The colors can be changed in the prompt section to one's liking, just don't mess with color values.&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${cyan}%n${blue}@%m ${yellow}%~ ${green}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;And here is a version that is used for normal users.

PATH should be set using &lt;code&gt;setenv PATH '/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11'&lt;/code&gt; and more paths added with a colon-delimited list in the rc file

==== Setting Desktop parameters ====
Use "Desktop-&gt;Customize-&gt;Utilities" from the toolchest menu to specify default applications. Using the full path is necessary. "Desktop-&gt;Customize-&gt;Icons" from the toolchest menu will set the icon size and enable the global setting "Open in Place" which prevents the file manager from creating a new window when opening a new directory.

==== Xdefaults file ====
Here is a sample configuration that dates to the Nekochan.net era:&lt;pre&gt;
*clientDecoration: +resizeh +border +minimize +maximize +menu

*DesksOverview*clientDecoration: none

4Dwm*clock*clientDecoration: none

Overview.geometry: +10-10

Overview*viewWindowName: true

Overview*Frame.marginHeight: 1

Overview*Frame.marginWidth: 1

4Dwm*interactivePlacement: False

4DWm*clientAutoPlace: False

4Dwm*usePPosition: True

4Dwm*positionOnScreen: True

4Dwm*iconImageBackground black

4Dwm*iconImageForeground: white

4Dwm*iconPlacement: left top tight

4Dwm*iconPlacementMargin: 1

4Dwm*resizeBorderWidth: 1

4Dwm*frameBorderWidth: 1

4Dwm*SG_frameOutline: false

4Dwm*SG_titleOutline: false

4Dwm*SG_titlePadding: 0

4Dwm*SG_useDecals: false

4Dwm*iconDecoration: label image
&lt;/pre&gt;The desktop can be heavily customized as needed. To customize 4Dwm, read its manpage

==== Setting up SSH ====
IRIX came with a very old OpenSSH version, and Nekoware has OpenSSH as well. However, these are no longer maintained. A better option is available at [[SSH Setup for 6.5]].

==== Amend toolchest ====
A full explanation of toolchest is available on its manpage. toolchest reads the following files:&lt;pre&gt;
/usr/lib/X11/system.chestrc

~/.chestrc

~/.auxchestrc

/usr/lib/X11/nodesktop.chestrc

/usr/lib/X11/app-chests/*.chest

/usr/lib/X11/app-defaults/Toolchest

/usr/lib/X11/remote.chestrc

The first three are relevant to most users. To remove entries, remove Itemname in a ~/.auxchestrc is sufficient. Creating entries is easy as well:

menu ToolChest

{

"My Favorite Things" f.menu mystuff

}

menu mystuff

{

"dolphins" f.exec "/usr/demos/bin/atlantis"

"Test Program" f.exec "source ~/.variables;~/testprog"

"games" f.menu mygames

}

menu mygames

{

"flight simulator" f.exec /usr/demos/bin/flight

"arena" f.exec /usr/demos/bin/arena

}
&lt;/pre&gt;Is the manpage example.

==== Setting Backgrounds ====
An article on this is available at Setting Backgrounds

=== Wrapping up ===
This is the end of IRIX Setup 101. For practical reasons this ends most common "first time" setup questions and was patterned after the popular, though poorly-written "IRIX Installation and Customization". Further guides will explore how to perform more advanced configurations.

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>7f63ca6f9d1afa80daa069ef6bfdaba6b73fd7d1</sha1>
  </revision>
  <revision>
    <id>326</id>
    <parentid>325</parentid>
    <timestamp>2025-02-24T04:37:08Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Setting Backgrounds */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12471" xml:space="preserve">For newcomers to IRIX, setting up IRIX for the first time can be daunting. This aims to break it down into selective, easy-to-follow sections for a post-install IRIX.

=== Forenotes ===
Due to specificity of various hardware and IRIX versions, this guide primarily assumes IRIX 6.5.21+ and that the user is interested in running Nekoware, optxeno, or another product offered on IRIXNet. It is advised to go into this understanding what the goals of the user are exactly.

Per the Style Guide all root commands will be prefixed with #, all user-level commands will be prefixed with % (for the tcsh shell).

=== First Steps ===

==== Securing root ====
Either login on the login screen to root, or serial in via root. Open a terminal window by clicking Desktop - &gt; Open Unix Shell. This is the root shell of the account, and for clarity sake, most commands will be performed via terminal. Type &lt;code&gt;# passwd&lt;/code&gt; and set a secure password for the root user. If doing this from GUI (i.e. EZSetup, this will cover most of the important settings covered there) be warned IRIX will not accept passwords greater than 8 chars in length. From the commandline, there is no such limitations.

==== Network Setup ====
A detailed article can be found at [[Network Setup]].

==== Date and Time ====
Again, a detailed article can be found at [[Keeping Time]].

==== Move $HOME for root ====
Now it is necessary to make a space for root. Due to IRIX's default install, root's home directory is effectively /, the root of the filesystem. '''This is bad. Do not skip this step.'''

Home directories are defined in &lt;code&gt;/etc/passwd&lt;/code&gt;. First, make the directory: &lt;code&gt;# mkdir /root; chmod go-wrx /root&lt;/code&gt; And then update the root line to look like so: &lt;code&gt;root::0:0:Super-User:/root:/bin/tcsh&lt;/code&gt; This can be automated (carefully) with a perl, awk, or sed command, but be careful.

Now clean up: &lt;code&gt;# cd /; rm -rf Desktop dumpster .Sgiresources .cshrc .login .profile .varupdate .wshttymode .desktop-IRIS .desktophost&lt;/code&gt;

Log out and log back in again.

=== Securing IRIX ===

==== Lock unsafe accounts ====
IRIX by default is installed with several accounts without passwords. Checking this is easy: &lt;code&gt;# passwd -as&lt;/code&gt;

Locking the accounts on a normal IRIX install is easy:

&lt;code&gt;# foreach account (lp EZsetup nuucp demos guest OutOfBox sys adm sysadm cmwlogin auditor dbadmin sgiweb 4Dgifts); passwd -l $account; end&lt;/code&gt;

==== Creating a user account ====
Next, create a user account for normal usage, as running as root 24/7 is dangerous. It's easily and safely done using tools in the privbin: &lt;code&gt;# /usr/sysadm/privbin/addUserAccount -l username -S `which tcsh` -H /usr/people/username -C -u 1034 -g 20&lt;/code&gt;

The above example will create a user called '''username''' with a default shell of tcsh, a home directory of &lt;code&gt;/usr/people/username&lt;/code&gt; (/home is NOT a thing on IRIX), create the directory (-C flag) with a uid of 1034 and membership in the user group (ID 20). It may also be advisable to create a group with the same username created by the command above, however that requires manually adding a group to &lt;code&gt;/etc/group&lt;/code&gt; and editing permissions on the home directory. This may be covered in a future installment.

==== Enable Shadow Passwords ====
By default IRIX uses crypt() hashes in /etc/passwd

This is now discouraged and insecure, so it is preferred to enable /etc/shadow. Run &lt;code&gt;pwconv&lt;/code&gt; to enable it.

==== Edit system defaults ====
The file &lt;code&gt;/etc/default/login&lt;/code&gt; controls primary login behavior. Edit the files options to look something akin to this:&lt;pre&gt;
CONSOLE=/dev/console

PASSREQ=YES

ALTSHELL=YES

MANDPASS=YES

UMASK=027

TIMEOUT=60

DISABLETIME=300

MAXTRYS=3

LOGFAILURES=4

IDLEWEEKS=2

PATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11:

SUPATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/etc:/usr/etc:/usr/bin/X11:

SYSLOG=ALL

INITGROUPS=YES

LANG=C

SVR4_SIGNALS=NO

LOCKOUT=4

LOCKOUTEXEMPT=root
&lt;/pre&gt;Note that it is a good opportunity to add extra pathnames that all users will have in PATH. Examples include /usr/nekoware/bin, /opt/xeno/bin, et cetera.

chmod the file to 444 next: &lt;code&gt;# chmod 444 /etc/default/login&lt;/code&gt;

==== File Alteration Monitor ====
For security reasons, edit &lt;code&gt;/etc/fam.conf&lt;/code&gt; to have local_only = true instead of local_only = false.

==== Disable Vulnerable Network Services ====
The following network services are wholly unnecessary for most installations and can be disabled with the following command string:&lt;pre&gt;
# chkconfig sgi_apache off; chkconfig webface_apache off; chkconfig appletalk off; \

chkconfig timed off; chkconfig timeslave off; chkconfig esp off; chkconfig ipaliases off; \

chkconfig ypmaster off; chkconfig yp off; chkconfig sendmail off; chkconfig sendmail_cf off; \

chkconfig webface off; chkconfig named off; chkconfig rsvpd off; chkconfig privileges off
&lt;/pre&gt;Additionally, disabling the following services in &lt;code&gt;/etc/inetd.conf&lt;/code&gt; is prudent, except telnet if an ssh server isn't installed yet, and the system is a server. If that's the case, hold off on that one:&lt;pre&gt;
finger

bootp

tftp

echo

telnet

ftp

discard

chargen

daytime

time

rstatd

walld

rusersd

rquotad

sprayd

ttdbserverd

shell

exec

http

wn-http

ntalk

mountd

sgi_mountd

rexd

bootparam

ypupdated

sgi_videod

sgi_toolkitbus

sgi_snoopd

sgi_pcsd

sgi_pod

sgi_espd

sgi-esphttp

tcpmux/sgi_scanner
&lt;/pre&gt;Some of the above can be re-enabled depending on what is necessary, but the esp ones should not be re-enabled.

==== Secure the X server ====
Edit &lt;code&gt;/var/X11/xdm/xdm-config&lt;/code&gt; and change the DisplayManager*authorize line to read: &lt;code&gt;DisplayManager*authorize: on&lt;/code&gt;

==== Tune the kernel for security ====
Changing these if they are not in use is prudent:&lt;pre&gt;
# printf 'y' | systune ipforwarding 0

# printf 'y' | systune ip6forwarding 0

# printf 'y' | systune icmp_dropredirects 1

# printf 'y' | systune tcp_2msl 60

# printf 'y' | systune allow_brdaddr_srcaddr 0

# printf 'y' | systune tcpiss_md5 1

# printf 'y' | systune restricted_chown 1

# printf 'y' | systune ncargs 131072

&lt;/pre&gt;run &lt;code&gt;# /etc/autoconfig -vf&lt;/code&gt; to rebuild the kernel, and then reboot for full changes to take effect.

==== Install Patches ====
A collection of patches obtained from user backups of sgi.com's support centre is here: &lt;nowiki&gt;http://ftp.irixnet.org/sgi-irix/patches/&lt;/nowiki&gt;

Install all patches for the IRIX version being ran. (inst will not install irrelevant patches on the system).

=== Customizing IRIX ===
Now that security is improved, the actual fun can begin to customizing the IRIX experience.

==== Setup flexlm ====
Place licenses for products in /var/flexlm/license.dat. Softwindows and a few others use different locations. There is a license file in the wiki as well. (search for it!)

==== Enable 24 bit X ====
Unless the graphics in the system are 8-bit (such as an Indy with an XL/8 card), enabling Truecolor will improve the user experience. Edit &lt;code&gt;/var/X11/xdm/Xservers&lt;/code&gt; to be &lt;code&gt;:0 secure /usr/bin/X11/X -bs -nobitscale -c -class TrueColor -depth 24 -solidroot sgilightblue -cursorFG red -cursorBG white&lt;/code&gt;

==== Enable scrollwheel. ====
IRIX by default can't use a scroll wheel. This can be rectified in the kernel:

&lt;code&gt;# systune pcmouse_mode 2&lt;/code&gt;

This sets the scroll wheel to work as on a PC. Mode 3 will set any additional buttons on the mouse to scroll. (it only detects 2 extra buttons)

==== Reduce gamma ====
Set gamma with the following command as root: &lt;code&gt;gamma 1.2&lt;/code&gt; or another value. This will lower the default to a more natural level.

==== Custom tcsh prompt ====
tcsh is a fast, simple UNIX shell that supports most of the same features as bash from an interactive standpoint, and is faster at startup.

Here is a configuration file for root:&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${red}%n${blue}@%m ${yellow}%~ ${red}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;


This sets a red prompt as a reminder. The colors can be changed in the prompt section to one's liking, just don't mess with color values.&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${cyan}%n${blue}@%m ${yellow}%~ ${green}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;And here is a version that is used for normal users.

PATH should be set using &lt;code&gt;setenv PATH '/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11'&lt;/code&gt; and more paths added with a colon-delimited list in the rc file

==== Setting Desktop parameters ====
Use "Desktop-&gt;Customize-&gt;Utilities" from the toolchest menu to specify default applications. Using the full path is necessary. "Desktop-&gt;Customize-&gt;Icons" from the toolchest menu will set the icon size and enable the global setting "Open in Place" which prevents the file manager from creating a new window when opening a new directory.

==== Xdefaults file ====
Here is a sample configuration that dates to the Nekochan.net era:&lt;pre&gt;
*clientDecoration: +resizeh +border +minimize +maximize +menu

*DesksOverview*clientDecoration: none

4Dwm*clock*clientDecoration: none

Overview.geometry: +10-10

Overview*viewWindowName: true

Overview*Frame.marginHeight: 1

Overview*Frame.marginWidth: 1

4Dwm*interactivePlacement: False

4DWm*clientAutoPlace: False

4Dwm*usePPosition: True

4Dwm*positionOnScreen: True

4Dwm*iconImageBackground black

4Dwm*iconImageForeground: white

4Dwm*iconPlacement: left top tight

4Dwm*iconPlacementMargin: 1

4Dwm*resizeBorderWidth: 1

4Dwm*frameBorderWidth: 1

4Dwm*SG_frameOutline: false

4Dwm*SG_titleOutline: false

4Dwm*SG_titlePadding: 0

4Dwm*SG_useDecals: false

4Dwm*iconDecoration: label image
&lt;/pre&gt;The desktop can be heavily customized as needed. To customize 4Dwm, read its manpage

==== Setting up SSH ====
IRIX came with a very old OpenSSH version, and Nekoware has OpenSSH as well. However, these are no longer maintained. A better option is available at [[SSH Setup for 6.5]].

==== Amend toolchest ====
A full explanation of toolchest is available on its manpage. toolchest reads the following files:&lt;pre&gt;
/usr/lib/X11/system.chestrc

~/.chestrc

~/.auxchestrc

/usr/lib/X11/nodesktop.chestrc

/usr/lib/X11/app-chests/*.chest

/usr/lib/X11/app-defaults/Toolchest

/usr/lib/X11/remote.chestrc

The first three are relevant to most users. To remove entries, remove Itemname in a ~/.auxchestrc is sufficient. Creating entries is easy as well:

menu ToolChest

{

"My Favorite Things" f.menu mystuff

}

menu mystuff

{

"dolphins" f.exec "/usr/demos/bin/atlantis"

"Test Program" f.exec "source ~/.variables;~/testprog"

"games" f.menu mygames

}

menu mygames

{

"flight simulator" f.exec /usr/demos/bin/flight

"arena" f.exec /usr/demos/bin/arena

}
&lt;/pre&gt;Is the manpage example.

==== Setting Backgrounds ====
An article on this is available at [[Setting Backgrounds]].

Wrapping up

This is the end of IRIX Setup 101. For practical reasons this ends most common "first time" setup questions and was patterned after the popular, though poorly-written "IRIX Installation and Customization". Further guides will explore how to perform more advanced configurations.

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>736c11b3b0beb2645f5395af1891ac9f97837e7a</sha1>
  </revision>
  <revision>
    <id>327</id>
    <parentid>326</parentid>
    <timestamp>2025-02-24T04:38:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Forenotes */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12424" xml:space="preserve">For newcomers to IRIX, setting up IRIX for the first time can be daunting. This aims to break it down into selective, easy-to-follow sections for a post-install IRIX.

== Forenotes ==
Due to specificity of various hardware and IRIX versions, this guide primarily assumes IRIX 6.5.21+ and that the user is interested in running Nekoware, optxeno, or another product offered on IRIXNet. It is advised to go into this understanding what the goals of the user are exactly.

Per the Style Guide all root commands will be prefixed with #, all user-level commands will be prefixed with % (for the tcsh shell).

== First Steps ==

=== Securing root ===
Either login on the login screen to root, or serial in via root. Open a terminal window by clicking Desktop - &gt; Open Unix Shell. This is the root shell of the account, and for clarity sake, most commands will be performed via terminal. Type &lt;code&gt;# passwd&lt;/code&gt; and set a secure password for the root user. If doing this from GUI (i.e. EZSetup, this will cover most of the important settings covered there) be warned IRIX will not accept passwords greater than 8 chars in length. From the commandline, there is no such limitations.

=== Network Setup ===
A detailed article can be found at [[Network Setup]].

=== Date and Time ===
Again, a detailed article can be found at [[Keeping Time]].

=== Move $HOME for root ===
Now it is necessary to make a space for root. Due to IRIX's default install, root's home directory is effectively /, the root of the filesystem. '''This is bad. Do not skip this step.'''

Home directories are defined in &lt;code&gt;/etc/passwd&lt;/code&gt;. First, make the directory: &lt;code&gt;# mkdir /root; chmod go-wrx /root&lt;/code&gt; And then update the root line to look like so: &lt;code&gt;root::0:0:Super-User:/root:/bin/tcsh&lt;/code&gt; This can be automated (carefully) with a perl, awk, or sed command, but be careful.

Now clean up: &lt;code&gt;# cd /; rm -rf Desktop dumpster .Sgiresources .cshrc .login .profile .varupdate .wshttymode .desktop-IRIS .desktophost&lt;/code&gt;

Log out and log back in again.

== Securing IRIX ==

=== Lock unsafe accounts ===
IRIX by default is installed with several accounts without passwords. Checking this is easy: &lt;code&gt;# passwd -as&lt;/code&gt;

Locking the accounts on a normal IRIX install is easy:

&lt;code&gt;# foreach account (lp EZsetup nuucp demos guest OutOfBox sys adm sysadm cmwlogin auditor dbadmin sgiweb 4Dgifts); passwd -l $account; end&lt;/code&gt;

=== Creating a user account ===
Next, create a user account for normal usage, as running as root 24/7 is dangerous. It's easily and safely done using tools in the privbin: &lt;code&gt;# /usr/sysadm/privbin/addUserAccount -l username -S `which tcsh` -H /usr/people/username -C -u 1034 -g 20&lt;/code&gt;

The above example will create a user called '''username''' with a default shell of tcsh, a home directory of &lt;code&gt;/usr/people/username&lt;/code&gt; (/home is NOT a thing on IRIX), create the directory (-C flag) with a uid of 1034 and membership in the user group (ID 20). It may also be advisable to create a group with the same username created by the command above, however that requires manually adding a group to &lt;code&gt;/etc/group&lt;/code&gt; and editing permissions on the home directory. This may be covered in a future installment.

=== Enable Shadow Passwords ===
By default IRIX uses crypt() hashes in /etc/passwd

This is now discouraged and insecure, so it is preferred to enable /etc/shadow. Run &lt;code&gt;pwconv&lt;/code&gt; to enable it.

=== Edit system defaults ===

The file &lt;code&gt;/etc/default/login&lt;/code&gt; controls primary login behavior. Edit the files options to look something akin to this:&lt;pre&gt;
CONSOLE=/dev/console

PASSREQ=YES

ALTSHELL=YES

MANDPASS=YES

UMASK=027

TIMEOUT=60

DISABLETIME=300

MAXTRYS=3

LOGFAILURES=4

IDLEWEEKS=2

PATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11:

SUPATH=/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/etc:/usr/etc:/usr/bin/X11:

SYSLOG=ALL

INITGROUPS=YES

LANG=C

SVR4_SIGNALS=NO

LOCKOUT=4

LOCKOUTEXEMPT=root
&lt;/pre&gt;Note that it is a good opportunity to add extra pathnames that all users will have in PATH. Examples include /usr/nekoware/bin, /opt/xeno/bin, et cetera.

chmod the file to 444 next: &lt;code&gt;# chmod 444 /etc/default/login&lt;/code&gt;

=== File Alteration Monitor ===
For security reasons, edit &lt;code&gt;/etc/fam.conf&lt;/code&gt; to have local_only = true instead of local_only = false.

=== Disable Vulnerable Network Services ===

The following network services are wholly unnecessary for most installations and can be disabled with the following command string:&lt;pre&gt;
# chkconfig sgi_apache off; chkconfig webface_apache off; chkconfig appletalk off; \

chkconfig timed off; chkconfig timeslave off; chkconfig esp off; chkconfig ipaliases off; \

chkconfig ypmaster off; chkconfig yp off; chkconfig sendmail off; chkconfig sendmail_cf off; \

chkconfig webface off; chkconfig named off; chkconfig rsvpd off; chkconfig privileges off
&lt;/pre&gt;Additionally, disabling the following services in &lt;code&gt;/etc/inetd.conf&lt;/code&gt; is prudent, except telnet if an ssh server isn't installed yet, and the system is a server. If that's the case, hold off on that one:&lt;pre&gt;
finger

bootp

tftp

echo

telnet

ftp

discard

chargen

daytime

time

rstatd

walld

rusersd

rquotad

sprayd

ttdbserverd

shell

exec

http

wn-http

ntalk

mountd

sgi_mountd

rexd

bootparam

ypupdated

sgi_videod

sgi_toolkitbus

sgi_snoopd

sgi_pcsd

sgi_pod

sgi_espd

sgi-esphttp

tcpmux/sgi_scanner
&lt;/pre&gt;Some of the above can be re-enabled depending on what is necessary, but the esp ones should not be re-enabled.

=== Secure the X server ===
Edit &lt;code&gt;/var/X11/xdm/xdm-config&lt;/code&gt; and change the DisplayManager*authorize line to read: &lt;code&gt;DisplayManager*authorize: on&lt;/code&gt;

=== Tune the kernel for security ===

Changing these if they are not in use is prudent:&lt;pre&gt;
# printf 'y' | systune ipforwarding 0

# printf 'y' | systune ip6forwarding 0

# printf 'y' | systune icmp_dropredirects 1

# printf 'y' | systune tcp_2msl 60

# printf 'y' | systune allow_brdaddr_srcaddr 0

# printf 'y' | systune tcpiss_md5 1

# printf 'y' | systune restricted_chown 1

# printf 'y' | systune ncargs 131072

&lt;/pre&gt;run &lt;code&gt;# /etc/autoconfig -vf&lt;/code&gt; to rebuild the kernel, and then reboot for full changes to take effect.

=== Install Patches ===
A collection of patches obtained from user backups of sgi.com's support centre is here: &lt;nowiki&gt;http://ftp.irixnet.org/sgi-irix/patches/&lt;/nowiki&gt;

Install all patches for the IRIX version being ran. (inst will not install irrelevant patches on the system).

== Customizing IRIX ==
Now that security is improved, the actual fun can begin to customizing the IRIX experience.

=== Setup flexlm ===
Place licenses for products in /var/flexlm/license.dat. Softwindows and a few others use different locations. There is a license file in the wiki as well. (search for it!)

=== Enable 24 bit X ===
Unless the graphics in the system are 8-bit (such as an Indy with an XL/8 card), enabling Truecolor will improve the user experience. Edit &lt;code&gt;/var/X11/xdm/Xservers&lt;/code&gt; to be &lt;code&gt;:0 secure /usr/bin/X11/X -bs -nobitscale -c -class TrueColor -depth 24 -solidroot sgilightblue -cursorFG red -cursorBG white&lt;/code&gt;

=== Enable scrollwheel. ===
IRIX by default can't use a scroll wheel. This can be rectified in the kernel:

&lt;code&gt;# systune pcmouse_mode 2&lt;/code&gt;

This sets the scroll wheel to work as on a PC. Mode 3 will set any additional buttons on the mouse to scroll. (it only detects 2 extra buttons)

=== Reduce gamma ===
Set gamma with the following command as root: &lt;code&gt;gamma 1.2&lt;/code&gt; or another value. This will lower the default to a more natural level.

=== Custom tcsh prompt ===
tcsh is a fast, simple UNIX shell that supports most of the same features as bash from an interactive standpoint, and is faster at startup.

Here is a configuration file for root:&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${red}%n${blue}@%m ${yellow}%~ ${red}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;

This sets a red prompt as a reminder. The colors can be changed in the prompt section to one's liking, just don't mess with color values.&lt;pre&gt;
# Prompt

set red="%{\033[1;31m%}"

set green="%{\033[0;32m%}"

set yellow="%{\033[1;33m%}"

set blue="%{\033[1;34m%}"

set magenta="%{\033[1;35m%}"

set cyan="%{\033[1;36m%}"

set white="%{\033[0;37m%}"

set end="%{\033[0m%}"

set prompt="${cyan}%n${blue}@%m ${yellow}%~ ${green}%%${end} "

# History

if ($?prompt) then

# An interactive shell — set some stuff up

set filec

set history = 1000

set savehist = (1000 merge)

set autolist = ambiguous

# Use history to aid expansion

set autoexpand

set autorehash

set mail = (/var/mail/$USER)

if ( $?tcsh ) then

bindkey "^W" backward-delete-word

bindkey -k up history-search-backward

bindkey -k down history-search-forward

endif

endif

# Fix some IRIXisms

stty intr ^C

setenv TERM xterm
&lt;/pre&gt;And here is a version that is used for normal users.

PATH should be set using &lt;code&gt;setenv PATH '/usr/sbin:/usr/bsd:/sbin:/usr/bin:/bin:/usr/bin/X11'&lt;/code&gt; and more paths added with a colon-delimited list in the rc file

=== Setting Desktop parameters ===
Use "Desktop-&gt;Customize-&gt;Utilities" from the toolchest menu to specify default applications. Using the full path is necessary. "Desktop-&gt;Customize-&gt;Icons" from the toolchest menu will set the icon size and enable the global setting "Open in Place" which prevents the file manager from creating a new window when opening a new directory.

=== Xdefaults file ===

Here is a sample configuration that dates to the Nekochan.net era:&lt;pre&gt;
*clientDecoration: +resizeh +border +minimize +maximize +menu

*DesksOverview*clientDecoration: none

4Dwm*clock*clientDecoration: none

Overview.geometry: +10-10

Overview*viewWindowName: true

Overview*Frame.marginHeight: 1

Overview*Frame.marginWidth: 1

4Dwm*interactivePlacement: False

4DWm*clientAutoPlace: False

4Dwm*usePPosition: True

4Dwm*positionOnScreen: True

4Dwm*iconImageBackground black

4Dwm*iconImageForeground: white

4Dwm*iconPlacement: left top tight

4Dwm*iconPlacementMargin: 1

4Dwm*resizeBorderWidth: 1

4Dwm*frameBorderWidth: 1

4Dwm*SG_frameOutline: false

4Dwm*SG_titleOutline: false

4Dwm*SG_titlePadding: 0

4Dwm*SG_useDecals: false

4Dwm*iconDecoration: label image
&lt;/pre&gt;The desktop can be heavily customized as needed. To customize 4Dwm, read its manpage

=== Setting up SSH ===
IRIX came with a very old OpenSSH version, and Nekoware has OpenSSH as well. However, these are no longer maintained. A better option is available at [[SSH Setup for 6.5]].

=== Amend toolchest ===

A full explanation of toolchest is available on its manpage. toolchest reads the following files:&lt;pre&gt;
/usr/lib/X11/system.chestrc

~/.chestrc

~/.auxchestrc

/usr/lib/X11/nodesktop.chestrc

/usr/lib/X11/app-chests/*.chest

/usr/lib/X11/app-defaults/Toolchest

/usr/lib/X11/remote.chestrc

The first three are relevant to most users. To remove entries, remove Itemname in a ~/.auxchestrc is sufficient. Creating entries is easy as well:

menu ToolChest

{

"My Favorite Things" f.menu mystuff

}

menu mystuff

{

"dolphins" f.exec "/usr/demos/bin/atlantis"

"Test Program" f.exec "source ~/.variables;~/testprog"

"games" f.menu mygames

}

menu mygames

{

"flight simulator" f.exec /usr/demos/bin/flight

"arena" f.exec /usr/demos/bin/arena

}
&lt;/pre&gt;Is the manpage example.

== Setting Backgrounds ==
An article on this is available at [[Setting Backgrounds]].

== Wrapping up ==
This is the end of IRIX Setup 101. For practical reasons this ends most common "first time" setup questions and was patterned after the popular, though poorly-written "IRIX Installation and Customization". Further guides will explore how to perform more advanced configurations.

[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>f6deecb5bec03c9e2bb1716782f53947ff96ccf7</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Setting Backgrounds</title>
  <ns>0</ns>
  <id>8</id>
  <revision>
    <id>328</id>
    <parentid>12</parentid>
    <timestamp>2025-02-24T04:40:07Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3189" xml:space="preserve">IRIX supports out of the box on both [[IRIX 6.5|6.5]] and pre-6.5 versions customized backgrounds. The procedure varies from version to version, however, as 6.5.22+ supports modern image formats, while versions prior do not.

== Preliminary Steps ==
Enabling 24-bit X is a major requirement. IRIX Setup 101 has a section on this. Next, copy the backgrounds configuration file.

&lt;code&gt;% cp /usr/lib/X11/system.backgrounds ~/.backgrounds&lt;/code&gt;

=== Using XPM files (Most versions of IRIX prior to 6.5.22) ===
IRIX supported 8-bit XPM files relatively early in development. Create a directory to hold backgrounds:

&lt;code&gt;% mkdir ~/backgrounds&lt;/code&gt;

Once the images are added, then create an entry in the .backgrounds file:&lt;pre&gt;
background "Anime"

command "-xpm /usr/people/neko/backgrounds/anime.xpm"

default "-xpm /usr/people/neko/backgrounds/anime.xpm"

readok "/usr/people/neko/backgrounds/anime.xpm"

This is an example created originally by Nekonoko.

The entry will be in Desktop -&gt; Customize -&gt; Background labeled "Anime"
&lt;/pre&gt;

==== Using IRIX's Native PNG/BMP/JPEG handler (6.5.22+) ====
IRIX 6.5.22+ simplified this process greatly. The same entry would be:&lt;pre&gt;
background "Anime"

default "-image /usr/people/neko/backgrounds/anime.jpg"
&lt;/pre&gt;Under 6.5.22.

A Nekochan.net user created this script to automate entry of backgrounds:&lt;pre&gt;
#!/bin/sh

BGDIR=$HOME/backgrounds

cp /usr/lib/X11/system.backgrounds $HOME/.backgrounds

chmod 644 .backgrounds

cd ${BGDIR}

for x in *.jpg *.xpm *.png *.bmp; do

case ${x} in

'*.jpg'|'*.xpm'|'*.png'|'*.bmp') ;;

*)

NAME=`echo ${x} | tr '.' ' ' | awk '{print $1}' | tr '_' ' '`

echo "" &gt;&gt; $HOME/.backgrounds

echo "background \""${NAME}"\"" &gt;&gt; $HOME/.backgrounds

echo "default \""-image ${BGDIR}/${x}"\"" &gt;&gt; $HOME/.backgrounds

;;

esac

done
&lt;/pre&gt;Update the BGDIR variable to change the directory.

=== Using xli ===

In Nekoware, and several other distributions, xli is available and can add the above functionality to older machines. Configure an entry this way:&lt;pre&gt;
background "Anime2"

command "-execute /usr/freeware/bin/xli -onroot -fork /usr/people/neko/backgrounds/anime2.jpg"

default "-execute /usr/freeware/bin/xli -onroot -fork /usr/people/neko/backgrounds/anime2.jpg"

exeok "/usr/freeware/bin/xli"

readok "/usr/people/neko/backgrounds/anime2.jpg
&lt;/pre&gt;xli is the easiest of the two to install as it has no additional dependencies. It's rather dated in that it does not support progressive JPEG or PNG so some backgrounds will need to be converted to standard JFIF or JPEG before xli can deal with them. xli also does not support pseudo transparency effects with some applications, a good example being X-Chat.

There are a couple of caveats to note when using 24-bit images. Desks Overview will not display background previews in the desk panes and desktop switching slows down dramatically, though that's less of an issue on newer hardware.

xli can also add a background to the login screen by editing &lt;code&gt;/usr/lib/X11/xdm/Xsetup&lt;/code&gt; at the top of the file. Add the following:

&lt;code&gt;/usr/nekoware/bin/xli -onroot /path/to/wallpaper/login_pix.jpg&lt;/code&gt;

Note that xli may have a different path installed.</text>
    <sha1>51a82bc54192103c87377b3ee79f798e24805757</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Keeping Time</title>
  <ns>0</ns>
  <id>9</id>
  <revision>
    <id>329</id>
    <parentid>13</parentid>
    <timestamp>2025-02-24T04:40:28Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1997" xml:space="preserve">Keeping time on IRIX is an easy to do, but less-than well documented thing. This article aims to educate users on the best ways to synchronize, keep time and manage it appropriately.

== UNIX Date and Time ==
IRIX, like all System V UNIX releases, centers around the &lt;code&gt;date&lt;/code&gt; command for timekeeping purposes. Date can set the time, tell the time, and format time in various fashions, down to the second (a limitation of the UNIX time() syscall). Examples can be found here, not all are directly supported by IRIX.

=== Automating Time Synchronization ===
Historically, IRIX used &lt;code&gt;timeslave&lt;/code&gt; and &lt;code&gt;timed&lt;/code&gt; to synchronize time. Examples of timeslave and timed can be found at those links.

Because of security concerns and how they are unmaintained, there are better alternatives included with IRIX. The simplest is ntpdate which can simply be invoked with &lt;code&gt;ntpdate us.pool.ntp.org&lt;/code&gt;, substituting a proper pool server in the user's home country for the us one. This can be placed into the crontab to run at a regular interval.

&lt;code&gt;ntpd&lt;/code&gt; is also available in SGI Freeware, Nekoware, and many other distributions for synchronizing the time. All that needs to be done is set a list of servers in &lt;code&gt;/etc/ntpd.conf&lt;/code&gt; ('''Warning: not all distributions will put ntpd here!!! Consult the distribution's maintainers if it's unclear where to set it''') and then &lt;code&gt;/etc/init.d/ntp&lt;/code&gt; (or the appropriate source for the initscript) needs to be started for the daemon to run. chkconfig is used to enable the daemon.

=== Timezone ===
Setting the timezone in IRIX is relatively easy. The file &lt;code&gt;/etc/TIMEZONE&lt;/code&gt; (This is case sensitive) is read at boot to set the system timezone. This is a text file and various strings can be inserted. "TZ=:Europe/Berlin" is a valid string, as is "TZ=:EST5EDT" or something similar. The nuances of this are in the &lt;nowiki&gt;https://nixdoc.net/man-pages/IRIX/man5/environ.5.html&lt;/nowiki&gt; environ manpage.</text>
    <sha1>05b636bfd833c455009d9ad0b661354bef26322a</sha1>
  </revision>
  <revision>
    <id>330</id>
    <parentid>329</parentid>
    <timestamp>2025-02-24T04:40:50Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2005" xml:space="preserve">Keeping time on [[IRIX 6.5]] is an easy to do, but less-than well documented thing. This article aims to educate users on the best ways to synchronize, keep time and manage it appropriately.

== UNIX Date and Time ==
IRIX, like all System V UNIX releases, centers around the &lt;code&gt;date&lt;/code&gt; command for timekeeping purposes. Date can set the time, tell the time, and format time in various fashions, down to the second (a limitation of the UNIX time() syscall). Examples can be found here, not all are directly supported by IRIX.

=== Automating Time Synchronization ===
Historically, IRIX used &lt;code&gt;timeslave&lt;/code&gt; and &lt;code&gt;timed&lt;/code&gt; to synchronize time. Examples of timeslave and timed can be found at those links.

Because of security concerns and how they are unmaintained, there are better alternatives included with IRIX. The simplest is ntpdate which can simply be invoked with &lt;code&gt;ntpdate us.pool.ntp.org&lt;/code&gt;, substituting a proper pool server in the user's home country for the us one. This can be placed into the crontab to run at a regular interval.

&lt;code&gt;ntpd&lt;/code&gt; is also available in SGI Freeware, Nekoware, and many other distributions for synchronizing the time. All that needs to be done is set a list of servers in &lt;code&gt;/etc/ntpd.conf&lt;/code&gt; ('''Warning: not all distributions will put ntpd here!!! Consult the distribution's maintainers if it's unclear where to set it''') and then &lt;code&gt;/etc/init.d/ntp&lt;/code&gt; (or the appropriate source for the initscript) needs to be started for the daemon to run. chkconfig is used to enable the daemon.

=== Timezone ===
Setting the timezone in IRIX is relatively easy. The file &lt;code&gt;/etc/TIMEZONE&lt;/code&gt; (This is case sensitive) is read at boot to set the system timezone. This is a text file and various strings can be inserted. "TZ=:Europe/Berlin" is a valid string, as is "TZ=:EST5EDT" or something similar. The nuances of this are in the &lt;nowiki&gt;https://nixdoc.net/man-pages/IRIX/man5/environ.5.html&lt;/nowiki&gt; environ manpage.</text>
    <sha1>3670026e1c08d2264b5217bc64a48a9345733d7e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>4D1-3.x</title>
  <ns>0</ns>
  <id>113</id>
  <revision>
    <id>331</id>
    <parentid>248</parentid>
    <timestamp>2025-02-24T05:04:58Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="390" xml:space="preserve">4D1-3.x was the final release of the 4D1 systems before they were officially called IRIX. It is also the final version to use [[4Sight]].

[[File:4d1-3.3-Demos.gif|left|thumb|4D1 Demo Set courtesy of sgistuff.net]]
[[File:4d1-3.3-term.gif|thumb|4D1 wsh terminal courtesy of sgistuff.net]]

== Changes over prior releases ==
Unknown at this time. 
[[Category:OS-Versions]]
[[Category:Stubs]]</text>
    <sha1>4aa1853e06d61f89d715b799c3161f1fca9f0137</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>GL2-1.x</title>
  <ns>0</ns>
  <id>149</id>
  <revision>
    <id>332</id>
    <timestamp>2025-02-24T05:06:14Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "GL2 1.x was used on the IRIS 1000 series of workstations, part of the larger [[68k-based SGIs (IRIS Series)]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="109" xml:space="preserve">GL2 1.x was used on the IRIS 1000 series of workstations, part of the larger [[68k-based SGIs (IRIS Series)]]</text>
    <sha1>dfebe2e5fd4eac8609677b111559c35cf5956234</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>SGI Freeware</title>
  <ns>0</ns>
  <id>96</id>
  <revision>
    <id>333</id>
    <parentid>244</parentid>
    <timestamp>2025-02-24T05:18:51Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="553" xml:space="preserve">SGI Freeware was an IRIX-compatible distribution of free and open source software built and distributed by SGI employees, and distributed on SGI media.

Distributed on 4 CDs, it hosted a variety of software and directly served as the inspiration for [[Nekoware]]

== Notable Software on Freeware ==

* GCC 3.3
* FLTK 1.1.3
* QT3
* GTK+2.4.0
* XMMS 1.2.7
* Python 2.1.1

=== Notes on Usage ===
Freeware is not recommended for use. Much of the software is 25+ years out of date. 
[[Category:Open-Source-Software]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>fbf0c8bea3d420bb3ebd5b9d131be888c31deeff</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>334</id>
    <parentid>294</parentid>
    <timestamp>2025-02-24T05:23:23Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4079" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  Visual Workstation Rebrands

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[About TechPubs]]
&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>8a7b4dacda4e433ff25f07b7eaf708adfe25e4ce</sha1>
  </revision>
  <revision>
    <id>340</id>
    <parentid>334</parentid>
    <timestamp>2025-02-24T05:37:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4108" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  Visual Workstation Rebrands

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;
				&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>d0a858e173b4ecfa349b84db2759777048f7d90e</sha1>
  </revision>
  <revision>
    <id>345</id>
    <parentid>340</parentid>
    <timestamp>2025-02-24T05:57:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4155" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  Visual Workstation Rebrands

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;  [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>e13c7e0551e3382395d264f581fe47cf491c4956</sha1>
  </revision>
  <revision>
    <id>349</id>
    <parentid>345</parentid>
    <timestamp>2025-02-24T15:18:37Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4167" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====

* [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  Visual Workstation Rebrands

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;  [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>5bae976d03da742eec0933fbbe04176632c74728</sha1>
  </revision>
  <revision>
    <id>351</id>
    <parentid>349</parentid>
    <timestamp>2025-02-24T17:31:45Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4169" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====

* [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Indigo2]]

• [[Onyx]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  Visual Workstation Rebrands

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>f7ed96949fbef24f29e7f2d1b7f94fafd968b0df</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>TechPubs Wiki:About</title>
  <ns>4</ns>
  <id>151</id>
  <revision>
    <id>337</id>
    <timestamp>2025-02-24T05:34:51Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Base setup</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="959" xml:space="preserve">TechPubs was founded in 2025 as part of Kazuo Kuroi's mission to provide a one-stop shop for IRIX documentation in all forms. It is currently under heavy development with new articles and information released regularly.

== Name==
TechPubs is the logical name for the site as SGI referred to its online manuals directory as Techpubs. Tech-pubs.net was purchased from the prior owner of the domain for an undisclosed sum.

== Architecture==
TechPubs is intended to consist of a wiki, backup of HTML-based SGI documentation, a manpage directory (Currently not online), and additional spaces as necessary to accommodate all forms of documentation.

==Sourcing of Information==

Citations are currently under constructions for articles and will be used where attribution is necessary. But in general, the main sources of information are:

* SGI Stuff
* The former Nekochan.net wiki.
* The former IRIXNet wiki (merged into TechPubs)
* Jurassic Tech Pubs
* 4Dwm.com</text>
    <sha1>53c4f36c0bb8c88fe8c98c45d69f1c2202388c77</sha1>
  </revision>
  <revision>
    <id>338</id>
    <parentid>337</parentid>
    <timestamp>2025-02-24T05:36:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Sourcing of Information */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="971" xml:space="preserve">TechPubs was founded in 2025 as part of Kazuo Kuroi's mission to provide a one-stop shop for IRIX documentation in all forms. It is currently under heavy development with new articles and information released regularly.

== Name==
TechPubs is the logical name for the site as SGI referred to its online manuals directory as Techpubs. Tech-pubs.net was purchased from the prior owner of the domain for an undisclosed sum.

== Architecture==
TechPubs is intended to consist of a wiki, backup of HTML-based SGI documentation, a manpage directory (Currently not online), and additional spaces as necessary to accommodate all forms of documentation.

==Sourcing of Information==

Citations are currently under constructions for articles and will be used where attribution is necessary. But in general, the main sources of information are:

* [[SGI Stuff]]
* The former Nekochan.net wiki.
* The former IRIXNet wiki (merged into TechPubs)
* [[Jurassic Tech Pubs]]
* [[4Dwm.com]]</text>
    <sha1>6df7bf461ef4ec1b8bf3760ba1505b0f4f38eb2b</sha1>
  </revision>
  <revision>
    <id>339</id>
    <parentid>338</parentid>
    <timestamp>2025-02-24T05:36:44Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Sourcing of Information */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="975" xml:space="preserve">TechPubs was founded in 2025 as part of Kazuo Kuroi's mission to provide a one-stop shop for IRIX documentation in all forms. It is currently under heavy development with new articles and information released regularly.

== Name==
TechPubs is the logical name for the site as SGI referred to its online manuals directory as Techpubs. Tech-pubs.net was purchased from the prior owner of the domain for an undisclosed sum.

== Architecture==
TechPubs is intended to consist of a wiki, backup of HTML-based SGI documentation, a manpage directory (Currently not online), and additional spaces as necessary to accommodate all forms of documentation.

==Sourcing of Information==

Citations are currently under constructions for articles and will be used where attribution is necessary. But in general, the main sources of information are:

* [[SGI Stuff]]
* The former Nekochan.net wiki.
* The former [[IRIXNet]] wiki (merged into TechPubs)
* [[Jurassic Tech Pubs]]
* [[4Dwm.com]]</text>
    <sha1>d06472d6e70788709be98e5b9a0ed9a0d6f1860b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>IRIX 101</title>
  <ns>0</ns>
  <id>12</id>
  <revision>
    <id>341</id>
    <parentid>168</parentid>
    <timestamp>2025-02-24T05:41:48Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5406" xml:space="preserve">This guide aims to educate new users to IRIX about the differences between IRIX and other UNIX and Unix-like systems. This includes through FAQs, explanations of how some parts of the OS work, and how a new user can adjust to these changes easily.

== A Brief History of IRIX ==
IRIX began life as an evolution of two earlier projects, [[GL2]] and [[RISC/OS]] (a product by MIPS Computer Systems, not the Acorn RISC OS), the latter of which was acquired by Silicon Graphics in 1992. GL2 code from the 68000-based IRIS machines was ported to System V R3, making [[4D1-3.x]] - the immediate predecessor of IRIX de jure, but defacto IRIX under the hood. 4D1-3.x utilized NeWS in the form of 4Sight, replacing MEX, the windowing system on GL2. When SGI acquired MIPS Computer Systems, RISCOS had many things taken from it to form IRIX 4, which used XSGI and the familiar 4DWM instead of 4Sight. IRIX now steadily advanced, with 6.x introducing XFS, and 6.5 introducing many more HPC elements to the OS. The last major release was 6.5 in 1998, but the OS continued minor development until 2006 with the discontinuation of all MIPS development by SGI and the migration to IA-64 and GNU/Linux, ending the reign of IRIX and effectively relegating it to maintenance mode.

Throughout the 1990s, IRIX was influential in many industries such as HPC, education, scientific, 3D graphics (Autodesk Maya began life as PowerAnimator on IRIX for example) and music production. This legacy is a huge contribution to continued hobbyist development of IRIX.

== Frequently Asked Questions ==

=== Is IRIX related to GNU/Linux? ===
IRIX's XFS filesystem was ported to the Linux kernel and continues to be a major filesystem on GNU/Linux. Beyond that, IRIX is entirely different, predating Linux by years of development.

=== What systems does IRIX run on? ===
IRIX runs on MIPS workstations produced by SGI, and a modified version of it underpins UNICOS/mp on the Cray X1 and X1E. Other than that, it cannot run on anything else.

=== What does IRIX use for GUI? ===
IRIX, like most UNIX systems uses X11, a proprietary variant called XSGI, and the window manager is called 4DWM - standing for 4D Window Manager (early SGI machines were called 4D, and this also hearkens back to 4Sight and 4D1, the old name for IRIX).

=== Why are machines that run IRIX expensive? ===
There are no new machines being produced, and high-end machines are in short supply. Less expensive machines can be had. We do not recommend using eBay to search, as the prices are usually extremely inflated.

=== What shell does IRIX use? It doesn't behave like Bash! ===
Most UNIX do not use bash. IRIX uses tcsh and ksh as shells. tcsh is the one that has many of the features users are after (history, tab completion of arguments, repeat last argument (!$, not ESC-.), and thus the recommended interactive shell. However, should a user prefer it is possible to use bash from Nekoware, or other sources. It's not recommended to replace the root shell with bash, however.

=== What startup system does IRIX use? ===
IRIX uses a customized System V init. It is not the same as GNU/Linux's former default (sysvinit).

=== Where are eth0, sda1, and why does ifconfig show nothing unless I append -a? ===
IRIX, similar to BSDs and System V UNIX OSes, names devices by driver, not type. The disk naming scheme is similar to Solaris and illumos, /dev/dsk/dksXdXsX, or disk, scsi bus id, drive id, slice ID. ifconfig shows nothing unless -a is hit because it's not the same code as GNU/Linux.

=== Where can I get the source to IRIX? ===
IRIX is closed source, and there was no major release of the source during its lifetime. Community efforts to free it from limbo are ongoing.

== Is USB supported? ==
Only HID, USB audio and some controllers are supported. No USB mass storage or cameras or anything like that.

=== Can I mount an ISO of IRIX software? ===
No, not within IRIX. IRIX has no loopback filesystem support. Additionally, IRIX software is distributed on EFS CDs, not Joliet/rockridge/iso9660 (the format that is specified by .iso) so don't use .iso - use .efs or .img

=== My backspace key doesn't work. ===
This is common on some configurations. To fix, type the following sequence into a shell: &lt;code&gt;stty erase CTRL-V BACKSPACE&lt;/code&gt; the caps indicate actual keys to hit, not actual things to type. This should result in either stty erase^H or stty erase^? or something similar.

=== CTRL-C doesn't do SIGINT ===
Fixable. &lt;code&gt;stty intr ^C&lt;/code&gt;

Both 11 and 12 can be permanently solved by adding those commands to .cshrc or .bashrc or .profile, depending on the shell used and such.

=== Where is nano? ===
GNU nano never was packed with IRIX. Get used to using vi, that's the default commandline editor. There's jot as well, a graphical editor, and nedit. Nano is available from many distributions.

=== Can IRIX be emulated? ===
MAME currently supports (slow) emulation of IRIX. Do not use qemu-irix - it's not designed to run actual IRIX software, it's designed as a hack for N64 devs to use the IDO/MIPSPro compilation suite to reverse engineer N64 games.

=== Inst doesn't help with dependencies? ===
IRIX is from an era where dependencies needed to all be supplied at once or in-order for a package manager to work. It does not currently support automatic dependency resolution at all.


[[Category:Tutorials]]
[[Category:No-Images]]</text>
    <sha1>b61be32941cab00567a6adbbed97c6d96e97afc1</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>TechPubs Wiki:Copyrights</title>
  <ns>4</ns>
  <id>153</id>
  <revision>
    <id>343</id>
    <timestamp>2025-02-24T05:55:34Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "==Spirit of content licensing of the TechPubs Wiki== TechPubs allows reuse of the content here for noncommercial purposes.   ==Content licensing==  Text content of TechPubs Wiki is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International, a.k.a. CC BY-NC-SA 4.0.  ==Licensing Information==  You are free to:  * '''Share''' — copy and redistribute the material in any medium or format * '''Adapt''' — remix, transform, and build upon the..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1672" xml:space="preserve">==Spirit of content licensing of the TechPubs Wiki==
TechPubs allows reuse of the content here for noncommercial purposes. 

==Content licensing==

Text content of TechPubs Wiki is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International, a.k.a. CC BY-NC-SA 4.0.

==Licensing Information==

You are free to:

* '''Share''' — copy and redistribute the material in any medium or format
* '''Adapt''' — remix, transform, and build upon the material
===The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: ===
* '''Attribution''' — You must give appropriate credit , provide a link to the license, and indicate if changes were made . You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
* '''NonCommercial''' — You may not use the material for commercial purposes .
* '''ShareAlike''' — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
* '''No additional restrictions''' — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
'''Notices:
You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation .'''
'''
No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.'''


[[Category:Organization]]</text>
    <sha1>341dc4ed969c52164947e1712420deb7eb91e7b2</sha1>
  </revision>
  <revision>
    <id>344</id>
    <parentid>343</parentid>
    <timestamp>2025-02-24T05:56:18Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Spirit of content licensing of the TechPubs Wiki */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1769" xml:space="preserve">==Spirit of content licensing of the TechPubs Wiki==
TechPubs allows reuse of the content here for noncommercial purposes. Outside of that restriction, the general spirit is to make good, ethical use of the content here.

==Content licensing==

Text content of TechPubs Wiki is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International, a.k.a. CC BY-NC-SA 4.0.

==Licensing Information==

You are free to:

* '''Share''' — copy and redistribute the material in any medium or format
* '''Adapt''' — remix, transform, and build upon the material
===The licensor cannot revoke these freedoms as long as you follow the license terms. Under the following terms: ===
* '''Attribution''' — You must give appropriate credit , provide a link to the license, and indicate if changes were made . You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
* '''NonCommercial''' — You may not use the material for commercial purposes .
* '''ShareAlike''' — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
* '''No additional restrictions''' — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
'''Notices:
You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation .'''
'''
No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.'''


[[Category:Organization]]</text>
    <sha1>5133f35ec88624812750518ed474bdbaead44ed4</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Visual Workstation 320</title>
  <ns>0</ns>
  <id>154</id>
  <revision>
    <id>346</id>
    <timestamp>2025-02-24T06:04:08Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The '''SGI Visual Workstation 320''' is an x86 workstation manufactured by SGI and designed to run Windows NT and GNU/Linux. The Visual Workstations are notable for their use of the Intel Pentium II and Intel Pentium III processors (rather than the 64-bit MIPS RISC architecture usually used in SGI computer products), but are fundamentally ARCS firmware systems regardless of their ISA used.   == Hardware == The 320 is capable of taking 2 Slot-1 Pentium II or III CPUs with..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="803" xml:space="preserve">The '''SGI Visual Workstation 320''' is an x86 workstation manufactured by SGI and designed to run Windows NT and GNU/Linux. The Visual Workstations are notable for their use of the Intel Pentium II and Intel Pentium III processors (rather than the 64-bit MIPS RISC architecture usually used in SGI computer products), but are fundamentally ARCS firmware systems regardless of their ISA used. 

== Hardware ==
The 320 is capable of taking 2 Slot-1 Pentium II or III CPUs with up to 1GB of system memory, shared between the GPU and CPU. Otherwise, it can take 3 3.3V PCI expansion cards. Architecturally, the COBALT graphics processor is related to the MIPS-powered [[O2]] system. 

== Operating System Support ==
It was designed to run Windows NT 4.0 and 2000 as well as several GNU/Linux distributions.</text>
    <sha1>e83cadb984a31ed545c047a7d92a135de7386343</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>Visual Workstation 540</title>
  <ns>0</ns>
  <id>155</id>
  <revision>
    <id>347</id>
    <timestamp>2025-02-24T06:04:52Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The '''SGI Visual Workstation 540''' is an x86 workstation manufactured by SGI and designed to run Windows NT and GNU/Linux. The Visual Workstations are notable for their use of the Intel Pentium II and Intel Pentium III processors (rather than the 64-bit MIPS RISC architecture usually used in SGI computer products), but are fundamentally ARCS firmware systems regardless of their ISA used.  == Hardware == The 540 is capable of taking 4 Slot-1 Pentium II or III CPUs with..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="801" xml:space="preserve">The '''SGI Visual Workstation 540''' is an x86 workstation manufactured by SGI and designed to run Windows NT and GNU/Linux. The Visual Workstations are notable for their use of the Intel Pentium II and Intel Pentium III processors (rather than the 64-bit MIPS RISC architecture usually used in SGI computer products), but are fundamentally ARCS firmware systems regardless of their ISA used.

== Hardware ==
The 540 is capable of taking 4 Slot-1 Pentium II or III CPUs with up to 2GB of system memory, shared between the GPU and CPU. Otherwise, it can take 3 3.3V PCI expansion cards. Architecturally, the COBALT graphics processor is related to the MIPS-powered [[O2]] system.

== Operating System Support ==
It was designed to run Windows NT 4.0 and 2000 as well as several GNU/Linux distributions.</text>
    <sha1>3cefd9ad2fc7081656b81acb126befacc850a25a</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>USB</title>
  <ns>0</ns>
  <id>157</id>
  <revision>
    <id>350</id>
    <timestamp>2025-02-24T15:19:52Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "USB is officially supported on IRIX in a very limited fashion on Chimera (Tezro, Fuel, Origin/Onyx 3000, Origin/Onyx 3x0, and the Onyx4)  == Classes Supported == invent.h defines four classes:  the root hub/controller  USB hubs  human interface devices  the graphics compositor (A peripheral used to composite multiple VPros into a single output)  == Device Support == The number of confirmed devices that work under IRIX is quite small, but users have reported the following..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1024" xml:space="preserve">USB is officially supported on IRIX in a very limited fashion on Chimera (Tezro, Fuel, Origin/Onyx 3000, Origin/Onyx 3x0, and the Onyx4)

== Classes Supported ==
invent.h defines four classes:

the root hub/controller

USB hubs

human interface devices

the graphics compositor (A peripheral used to composite multiple VPros into a single output)

== Device Support ==
The number of confirmed devices that work under IRIX is quite small, but users have reported the following can work:

Three-button/scroll wheel mice (It's unknown if mice with additional buttons work).

USB hubs

USB Audio (little documentation has survived Nekochan on this, but it is mentioned in dmedia documentation)

PCI USB cards (mostly USB 1.1 with a handful of 2.0 cards)

=== Card Support ===
Adaptec AUA 3020 Rev B (Rev A doesn't work)

Belkin F5U220

Belkin N10117

SGI USB PCI card, SGI part number 9210286

== Mass Storage ==
Mass storage was never an option on IRIX and the lack of interoperable filesystems complicates efforts to use this.</text>
    <sha1>7c7514cfa651cff4631e59fe54ba793d1ce07ca6</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>IRIX 6.2</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>353</id>
    <parentid>210</parentid>
    <timestamp>2025-02-24T17:51:59Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1001" xml:space="preserve">[[File:Indy-6.2 IRIX.webp|thumb|SGI Indy 6.2 IRIX showcase]]
IRIX 6.2 was released in early 1996 for multiple SGI desktops. The 6.x series is based on late 5.x code with 64-bit support in the OS being its major killer app. IRIX 6.3 and 6.4 are special releases of 6.2 for the O2 and Octane, Origin2000/Onyx2 and Origin 200. 6.2 is based on [[IRIX 5.3]] code.  

== Major Changes ==
* 64-bit kernel support and the new n32 ABI. 
* Removal of all 32-bit only IRIX platforms from the supported list (i.e. R2000 and R3000 systems). 
* Improved system stability. 
* XFS file system is default. EFS no longer supported for system installs. 
* VNode/VFS system imported, enabling new filesystems to be more easily added. 
* COFF applications no longer supported.

== Versioning ==
IRIX 6.2 uses 6.3 for the SGI O2 release, and 6.4 for the Octane, Origin 200, Origin 2000, and Onyx2 releases. These are all fundamentally the same OS with different version numbers. 
[[Category:OS-Versions]]
[[Category:Stubs]]</text>
    <sha1>bfe6647be054630abed15fb4136dcbe8e16be1c3</sha1>
  </revision>
  <revision>
    <id>354</id>
    <parentid>353</parentid>
    <timestamp>2025-02-24T17:52:55Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="940" xml:space="preserve">IRIX 6.2 was released in early 1996 for multiple SGI desktops. The 6.x series is based on late 5.x code with 64-bit support in the OS being its major killer app. IRIX 6.3 and 6.4 are special releases of 6.2 for the O2 and Octane, Origin2000/Onyx2 and Origin 200. 6.2 is based on [[IRIX 5.3]] code.  

== Major Changes ==
* 64-bit kernel support and the new n32 ABI. 
* Removal of all 32-bit only IRIX platforms from the supported list (i.e. R2000 and R3000 systems). 
* Improved system stability. 
* XFS file system is default. EFS no longer supported for system installs. 
* VNode/VFS system imported, enabling new filesystems to be more easily added. 
* COFF applications no longer supported.

== Versioning ==
IRIX 6.2 uses 6.3 for the SGI O2 release, and 6.4 for the Octane, Origin 200, Origin 2000, and Onyx2 releases. These are all fundamentally the same OS with different version numbers. 
[[Category:OS-Versions]]
[[Category:Stubs]]</text>
    <sha1>864b30afa5cdfe5ad472fd5b676a41c0dbedae61</sha1>
  </revision>
  <revision>
    <id>356</id>
    <parentid>354</parentid>
    <timestamp>2025-02-24T17:55:14Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1008" xml:space="preserve">[[File:IRIX 6.2 Indy Showcase.png|thumb|An IRIX 6.2 Indy Showcase]]
IRIX 6.2 was released in early 1996 for multiple SGI desktops. The 6.x series is based on late 5.x code with 64-bit support in the OS being its major killer app. IRIX 6.3 and 6.4 are special releases of 6.2 for the O2 and Octane, Origin2000/Onyx2 and Origin 200. 6.2 is based on [[IRIX 5.3]] code.  

== Major Changes ==
* 64-bit kernel support and the new n32 ABI. 
* Removal of all 32-bit only IRIX platforms from the supported list (i.e. R2000 and R3000 systems). 
* Improved system stability. 
* XFS file system is default. EFS no longer supported for system installs. 
* VNode/VFS system imported, enabling new filesystems to be more easily added. 
* COFF applications no longer supported.

== Versioning ==
IRIX 6.2 uses 6.3 for the SGI O2 release, and 6.4 for the Octane, Origin 200, Origin 2000, and Onyx2 releases. These are all fundamentally the same OS with different version numbers. 
[[Category:OS-Versions]]
[[Category:Stubs]]</text>
    <sha1>78b47f8d83acda98b27e69b3c577e2b4116b12a5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>File:IRIX 6.2 Indy Showcase.png</title>
  <ns>6</ns>
  <id>159</id>
  <revision>
    <id>355</id>
    <timestamp>2025-02-24T17:54:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25" xml:space="preserve">An IRIX 6.2 Indy Showcase</text>
    <sha1>a6ae541c98ca2580abeb8916440311c6423f5555</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-23 17:41:01+00|303">
  <title>File:IRIX 5.3 Desktop.png</title>
  <ns>6</ns>
  <id>160</id>
  <revision>
    <id>357</id>
    <timestamp>2025-02-24T17:56:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">IRIX 5.3 Desktop</text>
    <sha1>e31b49b4a432749f34f32cca515f5e3e9a01779d</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>IRIX 5.3</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>358</id>
    <parentid>211</parentid>
    <timestamp>2025-02-24T17:57:07Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="428" xml:space="preserve">[[File:IRIX 5.3 Desktop.png|thumb|The 5.3 desktop]]
IRIX 5.3 was released in November of 1994, the last of the IRIX 5.x series that began in March of 1993. IRIX 5.3 improved system stability and introduced many features of IRIX such as XFS (with the XFS release in 12/1994), ELF executables and more. It replaced [[IRIX 4.0]], and maintains compatibility with IRIX 4.0 by and large. 

[[Category:OS-Versions]]
[[Category:Stubs]]</text>
    <sha1>414f7c50f57947c3f5de61a517fada2e229640e5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>359</id>
    <parentid>351</parentid>
    <timestamp>2025-02-24T18:00:09Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4210" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====

* [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  Visual Workstation Rebrands

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>a23f91da1418e3ba8450fc085528dc0718b2a54e</sha1>
  </revision>
  <revision>
    <id>367</id>
    <parentid>359</parentid>
    <timestamp>2025-02-24T18:13:59Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Peripherals */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4211" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  Visual Workstation Rebrands

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>3ca1fc9e7ca350e2afd61c670d2f98d7676037ad</sha1>
  </revision>
  <revision>
    <id>380</id>
    <parentid>367</parentid>
    <timestamp>2025-02-24T19:51:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4306" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  Visual Workstation Rebrands

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.1 and 5.2]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>23cd56f5d197a40c5650b02dc45086d739f03012</sha1>
  </revision>
  <revision>
    <id>381</id>
    <parentid>380</parentid>
    <timestamp>2025-02-24T19:52:42Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4306" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  Visual Workstation Rebrands

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.0 and 5.1]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>ecb020f5d8a72c824ced33941dd1797611b6bb98</sha1>
  </revision>
  <revision>
    <id>387</id>
    <parentid>381</parentid>
    <timestamp>2025-02-24T20:30:03Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* x86-based SGIs */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4310" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  [[Visual Workstation Rebrands]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.0 and 5.1]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>edd6211147b96a39a1768597fb960cf19778d214</sha1>
  </revision>
  <revision>
    <id>391</id>
    <parentid>387</parentid>
    <timestamp>2025-02-24T20:42:12Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4410" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]

'''Resellers'''

• [[SGIDepot]]

• [[Mashek]]

• [http://www.bbsolutions.com/ B&amp;B Solutions]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  [[Visual Workstation Rebrands]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.0 and 5.1]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>2d709a2fe6589652007dd2cf157303094d6d181c</sha1>
  </revision>
  <revision>
    <id>396</id>
    <parentid>391</parentid>
    <timestamp>2025-02-24T20:53:54Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4635" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation.&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]

'''Resellers'''

• [[SGIDepot]]

• [[Mashek]]

• [http://www.bbsolutions.com/ B&amp;B Solutions]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  [[Visual Workstation Rebrands]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.0 and 5.1]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''SGI in Popular Culture''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;

__NOTOC__</text>
    <sha1>a227771f0742b9f111ed9c4e9ac8ece13ad8d1bb</sha1>
  </revision>
  <revision>
    <id>397</id>
    <parentid>396</parentid>
    <timestamp>2025-02-24T20:54:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4565" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation.&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]

'''Resellers'''

• [[SGIDepot]]

• [[Mashek]]

• [http://www.bbsolutions.com/ B&amp;B Solutions]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  [[Visual Workstation Rebrands]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.0 and 5.1]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''SGI in Popular Culture''' &lt;/div&gt;[[Jurassic Park]]
&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


__NOTOC__</text>
    <sha1>849421ab418d2ed0b6662a2eb0e41d34acf02b1c</sha1>
  </revision>
  <revision>
    <id>409</id>
    <parentid>397</parentid>
    <timestamp>2025-02-24T23:34:18Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4577" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation.&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]

'''Resellers'''

• [[SGIDepot]]

• [[Mashek]]

• [http://www.bbsolutions.com/ B&amp;B Solutions]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  [[Visual Workstation Rebrands]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.0 and 5.1]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
			&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''SGI in Popular Culture''' &lt;/div&gt;[[Jurassic Park]]
&lt;/div&gt;[[Nintendo 64]]
&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


__NOTOC__</text>
    <sha1>3ecf015fdf0378030624eea51749b6424b47decf</sha1>
  </revision>
  <revision>
    <id>411</id>
    <parentid>409</parentid>
    <timestamp>2025-02-24T23:55:38Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4578" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation.&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]

'''Resellers'''

• [[SGIDepot]]

• [[Mashek]]

• [http://www.bbsolutions.com/ B&amp;B Solutions]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  [[Visual Workstation Rebrands]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.0 and 5.1]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
		&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''SGI in Popular Culture''' &lt;/div&gt;[[Jurassic Park]]
&lt;/div&gt;[[Nintendo 64]]
&lt;/div&gt;
			&lt;/div&gt;
		
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


__NOTOC__</text>
    <sha1>dacb2f90ee04df62c5f6c208255ac01472c3fd6f</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>File:Origin 200 Plastics front.jpg</title>
  <ns>6</ns>
  <id>161</id>
  <revision>
    <id>360</id>
    <timestamp>2025-02-24T18:02:49Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="33" xml:space="preserve">Origin 200 with complete plastics</text>
    <sha1>3342ce5f13a923c7da02858a390cdbb15251a6bf</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>Origin 200</title>
  <ns>0</ns>
  <id>162</id>
  <revision>
    <id>361</id>
    <timestamp>2025-02-24T18:02:58Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The '''Origin 200''' is a midrange server replacing the SGI Challenge M. It is the server counterpart to the [[Octane]] but shares its architecture with the Origin 2000.  [[File:Origin 200 Plastics front.jpg|thumb|Origin 200 with complete plastics]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="249" xml:space="preserve">The '''Origin 200''' is a midrange server replacing the SGI Challenge M. It is the server counterpart to the [[Octane]] but shares its architecture with the Origin 2000.

[[File:Origin 200 Plastics front.jpg|thumb|Origin 200 with complete plastics]]</text>
    <sha1>0aa5d490019798a1fd1a5a3ab4a51a2ee6d7936a</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>SGUG RSE</title>
  <ns>0</ns>
  <id>101</id>
  <revision>
    <id>362</id>
    <parentid>317</parentid>
    <timestamp>2025-02-24T18:06:31Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1131" xml:space="preserve">SGUG RSE is a community effort of the Silicon Graphics User Group to develop software for IRIX using a ported version of RPM, along with tdnf and microdnf to provide package management and resolution. It essentially installs itself as a package without any interaction with the larger system. 

==== Toolchain ====
RSE uses [[GCC]] 9.2.0 which can cross compile with distcc on x86 systems. It uses RPM SPEC files (not to be confused with SGI SPEC files) to generate SRPMs. It is based on Fedora 31. 

==== Packages ====
As of 2025, RSE is still experimental but boasts over 1,000 "packages" of software, of which many are games, media and other software that is of relevance to SGI users.

== Bootstrapping ==
RSE can be installed by doing the following:

Use /usr/sysadm/privbin/modifyUserAccount to add the main user to group sys. 

&lt;code&gt;systune ncargs 262144&lt;/code&gt;

Download the RSE archives from [https://github.com/sgidevnet/sgug-rse/releases GitHub]

There are always three. 

Extract the archives as root to /usr. 

Use tdnf to search the repos. 
[[Category:Open-Source-Software]]
[[Category:No-Images]]
[[Category:Stubs]]</text>
    <sha1>aab9e6cbd5630860e628ccb7bcce1301959cc24b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>File:Octane2 Desktop.png</title>
  <ns>6</ns>
  <id>163</id>
  <revision>
    <id>363</id>
    <timestamp>2025-02-24T18:10:37Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="31" xml:space="preserve">An IRIX 6.5 desktop by Irinikus</text>
    <sha1>ec665b85a19f3bb8b8b3da37ac43c6d7e2ad83e1</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>IRIX 6.5</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>364</id>
    <parentid>209</parentid>
    <timestamp>2025-02-24T18:11:13Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1682" xml:space="preserve">IRIX 6.5 is the final major version of IRIX released first in 1998 to replace [[IRIX 6.2]]. Further incremental improvements were made from 1998 to 2006, with security updates ending in 2013 under Rackable Systems. 

== Improvements over IRIX 6.2 ==
[[File:Octane2 Desktop.png|thumb|An Octane2 desktop by Irinikus]]
IRIX 6.5's most notable improvement is standardized distribution. No more is a specific IRIX version needed for a specific machine. It includes support for all 64-bit capable SGIs with a few exceptions (e.g. the Crimson). 

=== New Features: ===
* OpenGL 1.1 support for all systems supported. 
* Desktop now called IRIX Interactive Desktop
* Improved security for remote X and other subsystems (safer defaults)
* Gigabit support
* Improved C library support. Compiler now supports C99. 
* MIPSPro replaces IDO/uopt as the main compiler backend.
* Later versions have Firewire and USB support.
* Later versions added OpenGL 1.2 support

=== Lifecycle ===
From 1998 to 2006 a new point release was released every quarter from .1 to .30. Security updates continued for 6.5.22 and higher until 2013. Shortly thereafter, SGI's Supportfolio site went offline. 

=== System Support ===
IRIX 6.5 through .22 supported all of the following systems:

* [[IRIS Indigo]] R4000
* [[Onyx|Onyx/Challenge R4000-R10000]]
* [[Indy]]
* [[Indigo2]]
* [[Onyx2]]
* [[Octane]]
* [[Origin 2000|Origin 2000 and 200]]
* [[Challenge S]]
* [[O2]]
* [[Fuel]]
* [[Origin 300]]
* [[Origin 350]]
* [[Origin 3000]]
* [[Tezro]]
* [[Onyx4]]

After 6.5.22, support for the following systems was dropped:

* IRIS Indigo
* Indy
* Indigo2
* Onyx/Challenge

[[Category:OS-Versions]]
[[Category:No-Images]]</text>
    <sha1>50f384bf578d387d1005824714124d4fd316658f</sha1>
  </revision>
  <revision>
    <id>366</id>
    <parentid>364</parentid>
    <timestamp>2025-02-24T18:12:12Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1659" xml:space="preserve">IRIX 6.5 is the final major version of IRIX released first in 1998 to replace [[IRIX 6.2]]. Further incremental improvements were made from 1998 to 2006, with security updates ending in 2013 under Rackable Systems. 

== Improvements over IRIX 6.2 ==
[[File:Octane2 Desktop.png|thumb|An Octane2 desktop by Irinikus]]
IRIX 6.5's most notable improvement is standardized distribution. No more is a specific IRIX version needed for a specific machine. It includes support for all 64-bit capable SGIs with a few exceptions (e.g. the Crimson). 

=== New Features: ===
* OpenGL 1.1 support for all systems supported. 
* Desktop now called IRIX Interactive Desktop
* Improved security for remote X and other subsystems (safer defaults)
* Gigabit support
* Improved C library support. Compiler now supports C99. 
* MIPSPro replaces IDO/uopt as the main compiler backend.
* Later versions have Firewire and USB support.
* Later versions added OpenGL 1.2 support

=== Lifecycle ===
From 1998 to 2006 a new point release was released every quarter from .1 to .30. Security updates continued for 6.5.22 and higher until 2013. Shortly thereafter, SGI's Supportfolio site went offline. 

=== System Support ===
IRIX 6.5 through .22 supported all of the following systems:

* [[IRIS Indigo]] R4000
* [[Onyx|Onyx/Challenge R4000-R10000]]
* [[Indy]]
* [[Indigo2]]
* [[Onyx2]]
* [[Octane]]
* [[Origin 2000|Origin 2000 and 200]]
* [[Challenge S]]
* [[O2]]
* [[Fuel]]
* [[Origin 300]]
* [[Origin 350]]
* [[Origin 3000]]
* [[Tezro]]
* [[Onyx4]]

After 6.5.22, support for the following systems was dropped:

* IRIS Indigo
* Indy
* Indigo2
* Onyx/Challenge

[[Category:OS-Versions]]</text>
    <sha1>11f11ee94b582dab9ea93c5048fdee46e05a4b0e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>IRIX 4.0</title>
  <ns>0</ns>
  <id>83</id>
  <revision>
    <id>365</id>
    <parentid>232</parentid>
    <timestamp>2025-02-24T18:11:47Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="479" xml:space="preserve">IRIX 4.0, introduced in September of 1991 with the IRIS Indigo workstation was the first version of IRIX to be officially named "IRIX." Replacing the [[4Sight]] NeWS-based [[4D1-3.x]] system, X11R4 using the IRIS Desktop (later called IRIX Interactive Desktop), and was the first version to be released on CD, as opposed to QIC tape.

[[File:Irix-4.0.1-img1.gif|thumb|IRIX 4.0.1 Desktop with IRIS Showcase. Courtesy of sgistuff.net]]


[[Category:OS-Versions]]
[[Category:Stubs]]</text>
    <sha1>77037f08568c08fb4afe98bfadb16a812a95f57b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>Jurassic Park</title>
  <ns>0</ns>
  <id>164</id>
  <revision>
    <id>368</id>
    <timestamp>2025-02-24T19:15:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The 1993 Hollywood film prominently features several SGI systems in various shots, including a [[Crimson]]. Additionally much of the CGI produced was produced on SGI hardware.   == Sequence of Events == During the part where Dennis Nedry shuts down the security system, he prevented Mr. Arnold (the system administrator for the park played by Samuel L. Jackson) from being able to make changes to the security grid. After typing in xwsh 3 times to access the security grid (i..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1204" xml:space="preserve">The 1993 Hollywood film prominently features several SGI systems in various shots, including a [[Crimson]]. Additionally much of the CGI produced was produced on SGI hardware. 

== Sequence of Events ==
During the part where Dennis Nedry shuts down the security system, he prevented Mr. Arnold (the system administrator for the park played by Samuel L. Jackson) from being able to make changes to the security grid. After typing in xwsh 3 times to access the security grid (in actuality the commands were pure Hollywood), the system's terminal says "YOU DIDN'T SAY THE MAGIC WORD" and over on Nedry's Macintosh an animated sequence of Nedry in an Elvis costume taunts "You didn't say the magic word, ah-ah-ahhh!".

Later, John Hammond orders to hard reset the power grid and the SGI monitor says "System Ready". Again, this is not congruent with an SGI boot sequence. 

At the climax where Lex Murphy uses the Crimson to re-enable the door locks, the program she uses is FSN, Filesystem Navigator. It's a 3D demo, and it would not have been used in such a time sensitive situation due to slow frame rates. She would have been better off typing the system path, but such tensions do not pay for Hollywood.</text>
    <sha1>d909757abc731be36024ed097eb940092f68ab2e</sha1>
  </revision>
  <revision>
    <id>369</id>
    <parentid>368</parentid>
    <timestamp>2025-02-24T19:23:30Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1357" xml:space="preserve">The 1993 Hollywood film prominently features several SGI systems in various shots, including a [[Crimson]]. Additionally much of the CGI produced was produced on SGI hardware. 

== Sequence of Events ==
During the part where Dennis Nedry shuts down the security system, he prevented Mr. Arnold (the system administrator for the park played by Samuel L. Jackson) from being able to make changes to the security grid. After typing in xwsh 3 times to access the security grid (in actuality the commands were pure Hollywood), the system's terminal says "YOU DIDN'T SAY THE MAGIC WORD" and over on Nedry's Macintosh an animated sequence of Nedry in an Elvis costume taunts "You didn't say the magic word, ah-ah-ahhh!".

Later, John Hammond orders to hard reset the power grid and the SGI monitor says "System Ready". Again, this is not congruent with an SGI boot sequence. 

At the climax where Lex Murphy uses the Crimson to re-enable the door locks, the program she uses is [[FSN]], Filesystem Navigator. It's a 3D demo, and it would not have been used in such a time sensitive situation due to slow frame rates. She would have been better off typing the system path, but such tensions do not pay for Hollywood.

== Jurassic Classic ==
Some [[IRIS Indigo]] and [[Crimson]] units have Jurassic Classic logos.

[[Category:Popular Culture]]
[[Category:No-Images]]</text>
    <sha1>01a58850d502340579b6a79a50eca211068f38e0</sha1>
  </revision>
  <revision>
    <id>394</id>
    <parentid>369</parentid>
    <timestamp>2025-02-24T20:49:29Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1454" xml:space="preserve">The 1993 Hollywood film prominently features several SGI systems in various shots, including a [[Crimson]]. Additionally much of the CGI produced was produced on SGI hardware. 

== Sequence of Events ==
During the part where Dennis Nedry shuts down the security system, he prevented Mr. Arnold (the system administrator for the park played by Samuel L. Jackson) from being able to make changes to the security grid. After typing in xwsh 3 times to access the security grid (in actuality the commands were pure Hollywood), the system's terminal says "YOU DIDN'T SAY THE MAGIC WORD" and over on Nedry's Macintosh an animated sequence of Nedry in an Elvis costume taunts "You didn't say the magic word, ah-ah-ahhh!".

Later, John Hammond orders to hard reset the power grid and the SGI monitor says "System Ready". Again, this is not congruent with an SGI boot sequence. 

At the climax where Lex Murphy uses the Crimson to re-enable the door locks, the program she uses is [[FSN]], Filesystem Navigator. It's a 3D demo, and it would not have been used in such a time sensitive situation due to slow frame rates. She would have been better off typing the system path, but such tensions do not pay for Hollywood.

== Jurassic Classic ==
Some [[IRIS Indigo]] and [[Crimson]] units have Jurassic Classic logos.

== FSN Recreations ==
Jtsiomb has submitted his version of FSN: https://github.com/jtsiomb/fsnav
[[Category:Popular Culture]]
[[Category:No-Images]]</text>
    <sha1>3e859dc0208f32b2d3f8e683fcb0dedb10c600fa</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>EFS</title>
  <ns>0</ns>
  <id>27</id>
  <revision>
    <id>370</id>
    <parentid>35</parentid>
    <timestamp>2025-02-24T19:26:16Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="943" xml:space="preserve">The Extent File System was the default filesystem used by IRIX from GL2-W2.4 (pre-IRIX 4.x) through IRIX 5.3. Additionally, it was the filesystem used for all CDs produced for IRIX by SGI.

== History ==
EFS was introduced in GL2-W2.4, a pre-IRIX System V based product to replace the original System V UFS. It was deprecated starting in 1994, with the release of an IRIX 5.3 XFS distribution, and replaced by XFS with IRIX 6.0 on all new installs.

== Details ==
The EFS filesystem is relatively primitive by modern standards, being a synchronous (non-journaling, no soft updates) filesystem with a fixed block size of 512 bytes. 

* Block size: 512-bytes
** Block 0: unused or contains a bootstrap program
** Block 1: superblock, contains file system metadata
* Maximum file system size: 8GB (224 or 16777214 blocks)
* Maximum individual file size: 2GB
* Number of fixed-files created by mkfs: 9

[[Category: Subsystems]]
[[Category: Stubs]]</text>
    <sha1>093df8c5bf89c8cc3c98b5c5de8ead4291dc091d</sha1>
  </revision>
  <revision>
    <id>371</id>
    <parentid>370</parentid>
    <timestamp>2025-02-24T19:26:57Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* History */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="960" xml:space="preserve">The Extent File System was the default filesystem used by IRIX from GL2-W2.4 (pre-IRIX 4.x) through IRIX 5.3. Additionally, it was the filesystem used for all CDs produced for IRIX by SGI.

== History ==
EFS was introduced in [[GL2-2.x|GL2-W2.4]], a pre-IRIX System V based product, to replace the original System V UFS. It was deprecated starting in 1994, with the release of an IRIX 5.3 XFS distribution, and replaced by [[XFS]] with IRIX 6.0 on all new installs.

== Details ==
The EFS filesystem is relatively primitive by modern standards, being a synchronous (non-journaling, no soft updates) filesystem with a fixed block size of 512 bytes. 

* Block size: 512-bytes
** Block 0: unused or contains a bootstrap program
** Block 1: superblock, contains file system metadata
* Maximum file system size: 8GB (224 or 16777214 blocks)
* Maximum individual file size: 2GB
* Number of fixed-files created by mkfs: 9

[[Category: Subsystems]]
[[Category: Stubs]]</text>
    <sha1>1078a8798c1c9da9a497b3a41b2ff88967701a2b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>File:IRIS 3130 Rebrand.jpg</title>
  <ns>6</ns>
  <id>165</id>
  <revision>
    <id>372</id>
    <timestamp>2025-02-24T19:34:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="69" xml:space="preserve">A rebranded 3130 workstation from the front. Courtesy of sgistuff.net</text>
    <sha1>65fbdfa6a91996fdb6c3e002f54dbfdd3744832a</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>File:IRIS 3130 Rebrand Rear.jpg</title>
  <ns>6</ns>
  <id>166</id>
  <revision>
    <id>373</id>
    <timestamp>2025-02-24T19:35:05Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="68" xml:space="preserve">A rebranded 3130 workstation from the rear. Courtesy of sgistuff.net</text>
    <sha1>3618313ed68f1a9e9c89f19badc2e1479ae41427</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>68k-based SGIs (IRIS Series)</title>
  <ns>0</ns>
  <id>98</id>
  <revision>
    <id>374</id>
    <parentid>298</parentid>
    <timestamp>2025-02-24T19:35:24Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2798" xml:space="preserve">[[File:SGI IRIS 2400.webp|thumb|An IRIS 2000 owned by System Source]]
The earliest SGI systems were 68000-68020 powered graphics terminals and workstations running [[GL2]], a System V UNIX with an unusual for the time focus on graphics. Multibus standard powered machines, they were similar to Sun Multibus systems in many respects.

They were replaced by the [[Professional IRIS]] series of systems.

== IRIS 1000 Series ==
[[File:IRIS 1000 Terminal.jpg|left|thumb|An IRIS 2000 Terminal]]
The 1000 and 1200 computers used a Motorola 68000 microprocessor clocked at 8 Mhz and were sold as diskless systems intended for use as a terminal to a VAX system. The mainboard in the IRIS 1x00 machines is of Sun origin, existing before the founding of Sun Microsystems.

=== IRIS 1400 and 1500 ===
The 1400 and 1500 were equipped with a 10 MHz Motorola 68010 microprocessor, 1.5 MB of RAM and supported ST-506 or SMD drives. IRIS 1400 and 1500 used [[GL2-1.x|GL2 operating system]], Version 1. It uses a Geometry Engine VLSI GPU and 8-bit graphics planes of 1024x1024 memory. Additional memory, a floating point unit and a faster CPU were available. 

== IRIS 2000 Series ==
The IRIS 2000 series includes the 2000 and 2200 terminals and the 2300, 2400 and 2500 workstations. These use the PM2 multibus board with a Motorola 68010 clocked at 10MHz. The SKYFPM-M-03 is an optional FPU board for these systems.  These systems supported a max of 2MB of RAM. [[GL2-2.x]] is the singular OS used by these.  

=== IRIS 2000 Turbo ===
The 2300, 2400 and 2500 were later updated with a Turbo board, which used the IP2 68020 CPU at 14MHz and the FP1 floating point accelerator. They supported a max of 16MB RAM. 

== IRIS Graphics ==
The IRIS Graphics system uses VLSI Geometry Engines and lacks any support for texturing. Within each GE is:

* 4 Matrix Engines
* 4-6 Clipper Engines
* 2 Scaler Engines

== IRIS 3000 Series ==
[[File:IRIS 3130 Rebrand.jpg|thumb|A rebranded 3130 workstation from the front. Courtesy of sgistuff.net]]
The IRIS 3000 series was the end of the Motorola 68000 line for SGI. All IRIS 3000s use the Motorola 68020 running at 16MHz. The 3010 is the singular terminal system, with the 3020, 3030, 3110, 3115, 3120, and 3130 all being workstations. All use the IP2 processor board which uses a private bus between the CPU, FPU and memory. The 3000 series uses a 10-GE Enhanced IRIS Graphics, which has 10GEs and 8 bitplanes with a max of 12MB for the terminal and 16MB for the workstations. 

[[GL2-3.x]] is the singular OS used by these. The later IRIS 3100 series uses a slightly enhanced IRIS Graphics boardset with 12 GEs, and a max of 32 bitplanes. 
[[File:IRIS 3130 Rebrand Rear.jpg|left|thumb|A rebranded 3130 workstation from the rear. Courtesy of sgistuff.net]]
[[Category:Hardware]]</text>
    <sha1>bdad608943706e8aa379e3f5f1684aaa29071efa</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>GL2-3.x</title>
  <ns>0</ns>
  <id>118</id>
  <revision>
    <id>375</id>
    <parentid>241</parentid>
    <timestamp>2025-02-24T19:36:26Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="457" xml:space="preserve">GL2-3.x was the final series released for the Motorola 68020-based [[68k-based SGIs (IRIS Series)|IRIS 3000 Series]] of terminals and workstations. GL2 uses the [[MEX]] windowing system. It was released concurrently with [[GL2-2.x]]

=== Changes from 2.x ===

* System V Shared Memory API
* [[File:MEX.png|thumb|MEX Demonstration on a 68k-based IRIS]]4.3BSD based TCP/IP stack
* NFSv1 and yp/NIS

[[Category:OS-Versions]]
[[Category:Stubs]]
[[Category:68k]]</text>
    <sha1>f9f9315e1759af1738df1008094cfb746454184e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>GL2-2.x</title>
  <ns>0</ns>
  <id>119</id>
  <revision>
    <id>376</id>
    <parentid>228</parentid>
    <timestamp>2025-02-24T19:37:55Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="430" xml:space="preserve">GL2-2.x was released in 1986 for the IRIS 1000 and 2000 68000-based SGI terminals and workstations. It is the origin of the [[EFS]] system which replaced the AT&amp;T UFS implementation. Replacing [[GL2-1.x]] which only ran on the IRIS 1000 series, it was a major improvement forward with TCP/IP stack, improved filesystem, and many other features. 

[[Category:OS-Versions]]
[[Category:No-Images]]
[[Category:Stubs]]
[[Category:68k]]</text>
    <sha1>aacea5f8083abfb39a0290fcc5c897bb9783c126</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>GL2-1.x</title>
  <ns>0</ns>
  <id>149</id>
  <revision>
    <id>377</id>
    <parentid>332</parentid>
    <timestamp>2025-02-24T19:38:53Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="273" xml:space="preserve">GL2 1.x was used on the IRIS 1000 series of workstations, part of the larger [[68k-based SGIs (IRIS Series)]].

== Survival? ==
Currently little to no information on GL2 1.x has survived including copies of the OS. Should one come across them, please contact the community.</text>
    <sha1>baba54f99eb238d4f2e3e2507278cf392d79585b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>TechPubs Wiki:Privacy policy</title>
  <ns>4</ns>
  <id>167</id>
  <revision>
    <id>378</id>
    <timestamp>2025-02-24T19:45:03Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "We provide this information for those who consult the TechPubs Wiki website. Note that this information applies only to that website and not to other websites the user may consult through links.   == Data controller ==  The data controller is Kazuo Kuroi (Raion), the admin of the wiki. .   == What data is collected == We do not collect any personal data.  In case of users login this Mediawiki, the following information is needed to provide the service to you and is store..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2461" xml:space="preserve">We provide this information for those who consult the TechPubs Wiki website. Note that this information applies only to that website and not to other websites the user may consult through links. 

== Data controller ==

The data controller is Kazuo Kuroi (Raion), the admin of the wiki. . 

== What data is collected ==
We do not collect any personal data.

In case of users login this Mediawiki, the following information is needed to provide the service to you and is stored as long as your account exists:

* Login credentials are stored in encrypted form and never shared with other parties.
* The IP address of your registration and of your last login are stored alongside the account. This is required to detect and delete spammer accounts. IP addresses of identified spammer accounts will be shared with other server operators to prevent further abuse.

'''Each user is responsible for the content they publish.'''

== Who can access the data, and for what activities? ==
The Wiki administrator can access Personally Identifiable Information (PII) also for technical needs.

=== Server Logs ===

To ensure proper operation of the service, including network and information security, the server log contain, among other data:

* Message meta-data (sender, receiver, type of message).
* Message content of messages automatically flagged as potential spam. These messages might undergo manual review.
* Connection information, including IP addresses and timestamps.
* Internal processing information.

== Scope of Privacy Laws == 
TechPubs, https://tech-pubs.net is published within the United States of America and US law thus applies. We offer this website internationally but we do not make any semblance of attempt to provide GDPR compliance. 

With that said, we will make good faith attempts to humor and respect users of TechPubs when requesting data or deleting data. We do not make any guarantees, but again, good faith attempts. 

== Data recipients ==
We do not communicate personal data collected from this website following its consultation to recipients or categories of recipients. 

== Period for storing personal data ==
This website stores personal data as described in the previous section "What data is collected" and "Server Logs" for the time related to the processing.

== Security measures ==
TechPubs adopts appropriate security measures to prevent unauthorized access, disclosure, modification, or unauthorized destruction of data.</text>
    <sha1>40a315b0faa4dcf3f6fb8026a97f1df994f5da1e</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>TechPubs Wiki:General disclaimer</title>
  <ns>4</ns>
  <id>168</id>
  <revision>
    <id>379</id>
    <timestamp>2025-02-24T19:49:25Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "&lt;div style="text-align: center; font-size: x-large; padding: 1em;"&gt;THE TECHPUBS WIKI MAKES NO GUARANTEE OF VALIDITY&lt;/div&gt;  TechPubs Wiki is an online open-content collaborative encyclopedia; that is, a voluntary association of individuals and groups working to develop a common resource of human knowledge. The structure of the project allows anyone with an Internet connection to alter its content.  Please be advised that nothing found here has necessarily been reviewed by..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4688" xml:space="preserve">&lt;div style="text-align: center; font-size: x-large; padding: 1em;"&gt;THE TECHPUBS WIKI MAKES NO GUARANTEE OF VALIDITY&lt;/div&gt;

TechPubs Wiki is an online open-content collaborative encyclopedia; that is, a voluntary association of individuals and groups working to develop a common resource of human knowledge. The structure of the project allows anyone with an Internet connection to alter its content.  Please be advised that nothing found here has necessarily been reviewed by people with the expertise required to provide you with complete, accurate or reliable information.

That is not to say that you will not find valuable and accurate information in TechPubs Wiki; much of the time you will.  However, '''TechPubs Wiki cannot guarantee the validity of the information found here.'''  The content of any given article may recently have been changed, vandalized or altered by someone whose opinion does not correspond with the state of knowledge in the relevant fields.  Note that most other encyclopedias and reference works [[:wikipedia:Wikipedia:Non-Wikipedia disclaimers|also have disclaimers]].

=== No formal peer review ===
Our active community of editors uses tools such as the [[Special:Recentchanges]] and [[Special:Newpages]] feeds to monitor new and changing content.  However, TechPubs Wiki is not uniformly peer reviewed; while readers may correct errors or engage in casual peer review, they have no legal duty to do so and thus all information read here is without any implied warranty of fitness for any purpose or use whatsoever.  Even articles that have been vetted by informal peer review may later have been edited inappropriately, just before you view them.

'''None of the contributors, sponsors, administrators or anyone else connected with TechPubs Wiki in any way whatsoever can be responsible for the appearance of any inaccurate or libelous information or for your use of the information contained in or linked from these web pages.'''

=== No contract; limited license ===
Please make sure that you understand that the information provided here is being provided freely, and that no kind of agreement or contract is created between you and the owners or users of this site, the owners of the servers upon which it is housed, the individual TechPubs Wiki contributors, any project administrators, sysops or anyone else who is in ''any way connected'' with this project or sister projects subject to your claims against them directly. You are being granted a limited license to copy anything from this site; it does not create or imply any contractual or extracontractual liability on the part of TechPubs Wiki or any of its agents, members, organizers or other users.

There is '''no agreement or understanding between you and TechPubs Wiki''' regarding your use or modification of this information beyond the neither is anyone at TechPubs Wiki responsible should someone change, edit, modify or remove any information that you may post on TechPubs Wiki or any of its associated projects.

=== Trademarks ===
Any of the trademarks, service marks, collective marks, design rights or similar rights that are mentioned, used or cited in the articles of the TechPubs Wiki encyclopedia are the property of their respective owners. Their use here does not imply that you may use them for any purpose other than for the same or a similar informational use as contemplated by the original authors of these TechPubs Wiki articles under the CC-BY-NC-SA licensing scheme. Unless otherwise stated TechPubs Wiki is neither endorsed by nor affiliated with any of the holders of any such rights and as such TechPubs Wiki cannot grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk.

=== Jurisdiction and legality of content ===
Publication of information found in TechPubs Wiki may be in violation of the laws of the country or jurisdiction from where you are viewing this information. The TechPubs Wiki database is stored on servers in the United States of America, and is maintained in reference to the protections afforded under local and federal law. Laws in your country or jurisdiction may not protect or allow the same kinds of speech or distribution.  TechPubs Wiki does not encourage the violation of any laws, and cannot be responsible for any violations of such laws, should you link to this domain or use, reproduce or republish the information contained herein.

=== Not professional advice ===
If you need specific advice (for example, medical, legal, financial or risk management), please seek a professional who is licensed or knowledgeable in that area.

[[Category:Policies]]</text>
    <sha1>2c4018c26ef62f139270db43c5f242230a7111ea</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>IRIX 5.0 and 5.1</title>
  <ns>0</ns>
  <id>169</id>
  <revision>
    <id>382</id>
    <timestamp>2025-02-24T20:03:00Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "IRIX 5.0.x and 5.1.x are infamous in the SGI community for quality and performance issues. As a result it is '''Not Recommended''' to run these versions.   == Causes of problems == "The primary cause is that we attempted far too much in too little time.  Management would not cut features early, so we were forced to make massive cuts in the final weeks of the release." is the words of Tom Davis, an SGI employee who posted a [http://www.sgistuff.net/software/irixintro/docu..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1191" xml:space="preserve">IRIX 5.0.x and 5.1.x are infamous in the SGI community for quality and performance issues. As a result it is '''Not Recommended''' to run these versions. 

== Causes of problems ==
"The primary cause is that we attempted far too much in too little time.  Management would not cut features early, so we were forced to make massive cuts in the final weeks of the release." is the words of Tom Davis, an SGI employee who posted a [http://www.sgistuff.net/software/irixintro/documents/irix-5.1.txt memo] to usenet. 

* Management in 1992 and 1993 attempted to push too many features in too little time. 
* Much of the desktop code was rewritten to use C++ and [[Viewkit]], neither of which were mature. 
* Tom indicated that the system requirements were too narrow for a 16MB base config of an Indy or similar. 
* Compile times were increased due to this system load, resulting in less attention paid to optimizing. 
* Dynamically linked libraries were introduced around this release, causing problems due to immaturity. 
* Poor team structure. Tom indicates that there was nobody really calling the right shots or even listening to one another due to lack of a project lead.

[[Category:stubs]]</text>
    <sha1>4dbe41988f4cde2f6091b2995acffa7cae6190c0</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>IRIXNet Proposed Swap Meet</title>
  <ns>0</ns>
  <id>170</id>
  <revision>
    <id>383</id>
    <timestamp>2025-02-24T20:09:15Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "Raion has interest in doing a swap meet type event in the near future. This page serves to document some of his ideas.   == Location and Venue == Richmond, Virginia is a logical choice. One proposed location is [https://accashriners.com/room-rental/ The Acca Shriners Hall] which is rented out for reasonable rates.   == Logistics ==  * Venue * Food * Tables and chairs * Payment Processors? * Security"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="402" xml:space="preserve">Raion has interest in doing a swap meet type event in the near future. This page serves to document some of his ideas. 

== Location and Venue ==
Richmond, Virginia is a logical choice. One proposed location is [https://accashriners.com/room-rental/ The Acca Shriners Hall] which is rented out for reasonable rates. 

== Logistics ==

* Venue
* Food
* Tables and chairs
* Payment Processors?
* Security</text>
    <sha1>7c298d81d50b84d17f2a019b2a6cb613ff0b8fcd</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>Power Series</title>
  <ns>0</ns>
  <id>117</id>
  <revision>
    <id>384</id>
    <parentid>230</parentid>
    <timestamp>2025-02-24T20:24:53Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2264" xml:space="preserve">The PowerSeries systems are the first multiprocessor computers made by Silicon Graphics and were typically shipped in a single or twin tower case. PowerSeries systems were first produced in twin tower shaped chassis similar to the [[Professional IRIS]], and later on single tower chassis was introduced. The high-end systems (more than 4 CPUs) were shipped in a full size rack due to space limitations in the desk-side cases.  

== Hardware ==
{| class="wikitable"
|Model
|CPU board
|CPU
|CPU Count
|Chassis
|-
|4D/120
|IP5
|R2000 16.7 MHz
|2
|Deskside
|-
|4D/210
|IP9
|R3000 25MHz
|1
|Deskside
|-
|4D/2x0
|IP7
|R3000 25MHz
|1-8
|Deskside or Rack
|-
|4D/3x0
|IP7
|R3000 33MHz
|1-8
|Deskside or Rack
|-
|4D/4x0
|IP15
|R3000 40MHz
|1-8
|Deskside or Rack
|}
[[File:4d380 rack.jpg|thumb|A 4D/380 owned by Jan-Jaap on the IRIXNet forums]]
The second digit indicates the original CPU configuration, e.g. a 4D/440 has 4 CPUs, a 4D/280 has 8. 

=== System Bus ===
The Processor Bus is a local bus that includes both an 100MB/s data and 100MB/s address bus which connects each processor with it's associated cache. The Sync Bus synchronizes the processors of the system and thus helps in parallel processing of data/programs. MPLink is an asynchronous bus that connects the CPUs and Memory as well as the other Subsystems of the PowerSeries computer.

=== CPU Boards ===
Systems are allowed to have 1 singleprocessor CPU board or up to 2/4 (deskside/rack) dualprocessor CPU boards. So valid numbers of CPUs are 1, 2, 4, 6 and 8. Mixing singleprocessor CPU boards with dualprocessor boards is not supported, but still may work.

The processor boards installed should be of the same type (e.g. all 25MHz IP7) but this is not a requirement. It is known that mixed setups can boot and operate just fine. Implications on CPU performance have not been tested yet but the basic operation is confirmed. The recommended setup is to have the faster CPU board goes into the first slot so that IRIX itself boots on the fastest CPU in the machine.

=== Graphics ===
[[File:4d380 open rack.jpeg|left|thumb|A 4D/380 open ]]
The systems support GTX/GTXB, VGX/VGXT and Reality Engine configurations as well as headless units. 
[[Category:Hardware]]
[[Category:Stubs]]
[[Category:No-Images]]</text>
    <sha1>3998a3a96bb92156ce5530012cf1297353760bda</sha1>
  </revision>
  <revision>
    <id>385</id>
    <parentid>384</parentid>
    <timestamp>2025-02-24T20:26:34Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2385" xml:space="preserve">The PowerSeries systems are the first multiprocessor computers made by Silicon Graphics and were typically shipped in a single or twin tower case. PowerSeries systems were first produced in twin tower shaped chassis similar to the [[Professional IRIS]], and later on single tower chassis was introduced. The high-end systems (more than 4 CPUs) were shipped in a full size rack due to space limitations in the desk-side cases.  

== Hardware ==
{| class="wikitable"
|Model
|CPU board
|CPU
|CPU Count
|Chassis
|-
|4D/120
|IP5
|R2000 16.7 MHz
|2
|Deskside
|-
|4D/210
|IP9
|R3000 25MHz
|1
|Deskside
|-
|4D/2x0
|IP7
|R3000 25MHz
|1-8
|Deskside or Rack
|-
|4D/3x0
|IP7
|R3000 33MHz
|1-8
|Deskside or Rack
|-
|4D/4x0
|IP15
|R3000 40MHz
|1-8
|Deskside or Rack
|}
[[File:4d380 rack.jpg|thumb|A 4D/380 owned by Jan-Jaap on the IRIXNet forums]]
The second digit indicates the original CPU configuration, e.g. a 4D/440 has 4 CPUs, a 4D/280 has 8. 

=== System Bus ===
The Processor Bus is a local bus that includes both an 100MB/s data and 100MB/s address bus which connects each processor with it's associated cache. The Sync Bus synchronizes the processors of the system and thus helps in parallel processing of data/programs. MPLink is an asynchronous bus that connects the CPUs and Memory as well as the other Subsystems of the PowerSeries computer.

=== CPU Boards ===
Systems are allowed to have 1 singleprocessor CPU board or up to 2/4 (deskside/rack) dualprocessor CPU boards. So valid numbers of CPUs are 1, 2, 4, 6 and 8. Mixing singleprocessor CPU boards with dualprocessor boards is not supported, but still may work.

The processor boards installed should be of the same type (e.g. all 25MHz IP7) but this is not a requirement. It is known that mixed setups can boot and operate just fine. Implications on CPU performance have not been tested yet but the basic operation is confirmed. The recommended setup is to have the faster CPU board goes into the first slot so that IRIX itself boots on the fastest CPU in the machine.

=== Graphics ===
[[File:4d380 open rack.jpeg|left|thumb|A 4D/380 open ]]
The systems support GTX/GTXB, VGX/VGXT and Reality Engine configurations as well as headless units. 

== Operating System Support ==
The final release to support these was IRIX 5.3, however the early models support [[4D1-3.x]]. The middle ground is [[IRIX 4.0]]. 
[[Category:Hardware]]</text>
    <sha1>5394c5cc0eca2ec2b514c2f57fd6e06f4d78785e</sha1>
  </revision>
  <revision>
    <id>386</id>
    <parentid>385</parentid>
    <timestamp>2025-02-24T20:28:46Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2546" xml:space="preserve">The PowerSeries systems are the first multiprocessor computers made by Silicon Graphics and were typically shipped in a single or twin tower case. PowerSeries systems were first produced in twin tower shaped chassis similar to the [[Professional IRIS]], and later on single tower chassis was introduced. The high-end systems (more than 4 CPUs) were shipped in a full size rack due to space limitations in the desk-side cases.  

== Hardware ==
{| class="wikitable"
|Model
|CPU board
|CPU
|CPU Count
|Chassis
|-
|4D/120
|IP5
|R2000 16.7 MHz
|2
|Deskside
|-
|4D/210
|IP9
|R3000 25MHz
|1
|Deskside
|-
|4D/2x0
|IP7
|R3000 25MHz
|1-8
|Deskside or Rack
|-
|4D/3x0
|IP7
|R3000 33MHz
|1-8
|Deskside or Rack
|-
|4D/4x0
|IP15
|R3000 40MHz
|1-8
|Deskside or Rack
|}
[[File:4d380 rack.jpg|thumb|A 4D/380 owned by Jan-Jaap on the IRIXNet forums]]
The second digit indicates the original CPU configuration, e.g. a 4D/440 has 4 CPUs, a 4D/280 has 8. 

=== System Bus ===
The Processor Bus is a local bus that includes both an 100MB/s data and 100MB/s address bus which connects each processor with it's associated cache. The Sync Bus synchronizes the processors of the system and thus helps in parallel processing of data/programs. MPLink is an asynchronous bus that connects the CPUs and Memory as well as the other Subsystems of the PowerSeries computer.

=== CPU Boards ===
Systems are allowed to have 1 singleprocessor CPU board or up to 2/4 (deskside/rack) dualprocessor CPU boards. So valid numbers of CPUs are 1, 2, 4, 6 and 8. Mixing singleprocessor CPU boards with dualprocessor boards is not supported, but still may work.

The processor boards installed should be of the same type (e.g. all 25MHz IP7) but this is not a requirement. It is known that mixed setups can boot and operate just fine. Implications on CPU performance have not been tested yet but the basic operation is confirmed. The recommended setup is to have the faster CPU board goes into the first slot so that IRIX itself boots on the fastest CPU in the machine.

=== Graphics ===
[[File:4d380 open rack.jpeg|left|thumb|A 4D/380 open ]]
The systems support GTX/GTXB, VGX/VGXT and Reality Engine configurations as well as headless units. 

== Operating System Support ==
The final release to support these was IRIX 5.3, however the early models support [[4D1-3.x]]. The middle ground is [[IRIX 4.0]]. 

== Final Notes ==
The photos of the rack unit were provided by Jan Jaap of IRIXNet. His thread can be found [https://forums.irixnet.org/thread-1471.html here].
[[Category:Hardware]]</text>
    <sha1>911cb4030e0469cb4de3c76a218197242ba2bf59</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>File:Stock Image of a VW 230.jpg</title>
  <ns>6</ns>
  <id>171</id>
  <revision>
    <id>388</id>
    <timestamp>2025-02-24T20:34:56Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23" xml:space="preserve">Stock image of a VW 230</text>
    <sha1>55119c2fa69cd7ec937ffb6335fa5da126be7802</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>Visual Workstation Rebrands</title>
  <ns>0</ns>
  <id>172</id>
  <revision>
    <id>389</id>
    <timestamp>2025-02-24T20:35:03Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "[[File:Stock Image of a VW 230.jpg|thumb|Stock image of a VW 230]] Unlike the [[Visual Workstation 320]] and its larger counterpart, the [[Visual Workstation 540]], the other members of the line were rebranded PCs, as were all other SGI-branded PC and servers using x86 from before their sale to Rackable Systems.   == Model Info == The 230, 330, and 550 models are essentially standard PCs and have the same capabilities and upgrade limits as other PCs of the time. The 230..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="820" xml:space="preserve">[[File:Stock Image of a VW 230.jpg|thumb|Stock image of a VW 230]]
Unlike the [[Visual Workstation 320]] and its larger counterpart, the [[Visual Workstation 540]], the other members of the line were rebranded PCs, as were all other SGI-branded PC and servers using x86 from before their sale to Rackable Systems. 

== Model Info ==
The 230, 330, and 550 models are essentially standard PCs and have the same capabilities and upgrade limits as other PCs of the time. The 230 and 330 are based on VIA chipsets, used socket 370 processors, and conventional SDRAM. The 550 used Slot 2 Xeon processors, the Intel 840 chipset, and RDRAM. The video cards these systems used are Nvidia AGP cards based on the Quadro 2 chipset, and differ from aftermarket Quadro GPUs in their drivers.

[[Category: Hardware]]
[[Category:Stubs]]</text>
    <sha1>15efd3ba95acf5506d1ba3bb8c1cd1ae700ed5dc</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>SGIDepot</title>
  <ns>0</ns>
  <id>173</id>
  <revision>
    <id>390</id>
    <timestamp>2025-02-24T20:39:36Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "'''SGIDepot''' is a website run by Ian Mapleson, a Scottish reseller of SGIs.   == Contents == Ian's website has sections for sale of his stock, but also containing:  * Buyers guide, benchmarks and other pertinent info.  * Install and sysadmin guides.  * Some PDFs and datasheets.  * Explanations of various graphics functions."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="327" xml:space="preserve">'''SGIDepot''' is a website run by Ian Mapleson, a Scottish reseller of SGIs. 

== Contents ==
Ian's website has sections for sale of his stock, but also containing:

* Buyers guide, benchmarks and other pertinent info. 
* Install and sysadmin guides. 
* Some PDFs and datasheets. 
* Explanations of various graphics functions.</text>
    <sha1>522deb1b245e40b76886a32cb586e656edcd5d78</sha1>
  </revision>
  <revision>
    <id>393</id>
    <parentid>390</parentid>
    <timestamp>2025-02-24T20:44:32Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="350" xml:space="preserve">'''SGIDepot''' is a website run by Ian Mapleson, a Scottish reseller of SGIs. https://sgidepot.co.uk 

== Contents ==
Ian's website has sections for sale of his stock, but also containing:

* Buyers guide, benchmarks and other pertinent info. 
* Install and sysadmin guides. 
* Some PDFs and datasheets. 
* Explanations of various graphics functions.</text>
    <sha1>ad3b65ccbe3f7c039ab3337179d02d22bc80522d</sha1>
  </revision>
  <revision>
    <id>403</id>
    <parentid>393</parentid>
    <timestamp>2025-02-24T21:33:42Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Contents */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="349" xml:space="preserve">'''SGIDepot''' is a website run by Ian Mapleson, a Scottish reseller of SGIs. http://sgidepot.co.uk 

== Contents ==
Ian's website has sections for sale of his stock, but also containing:

* Buyers guide, benchmarks and other pertinent info. 
* Install and sysadmin guides. 
* Some PDFs and datasheets. 
* Explanations of various graphics functions.</text>
    <sha1>5f545e7842084586d772db29229288847648d3bc</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>Mashek</title>
  <ns>0</ns>
  <id>174</id>
  <revision>
    <id>392</id>
    <timestamp>2025-02-24T20:43:45Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "'''Doug Mashek''' is an SGI reseller based in Tennessee. His website displays parts lists which can be useful for part identification."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">'''Doug Mashek''' is an SGI reseller based in Tennessee. His website displays parts lists which can be useful for part identification.</text>
    <sha1>7be47ab62553d7ba87d13c50af0f1891993768e0</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>TechPubs Wiki:About</title>
  <ns>4</ns>
  <id>151</id>
  <revision>
    <id>395</id>
    <parentid>339</parentid>
    <timestamp>2025-02-24T20:51:35Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Sourcing of Information */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1036" xml:space="preserve">TechPubs was founded in 2025 as part of Kazuo Kuroi's mission to provide a one-stop shop for IRIX documentation in all forms. It is currently under heavy development with new articles and information released regularly.

== Name==
TechPubs is the logical name for the site as SGI referred to its online manuals directory as Techpubs. Tech-pubs.net was purchased from the prior owner of the domain for an undisclosed sum.

== Architecture==
TechPubs is intended to consist of a wiki, backup of HTML-based SGI documentation, a manpage directory (Currently not online), and additional spaces as necessary to accommodate all forms of documentation.

==Sourcing of Information==

Citations are currently under constructions for articles and will be used where attribution is necessary. But in general, the main sources of information are:

* [https://sgistuff.net SGI Stuff]
* The former Nekochan.net wiki.
* The former [[IRIXNet]] wiki (merged into TechPubs)
* [https://techpubs.jurassic.nl Jurassic Tech Pubs]
* [https://4dwm.com 4Dwm.com]</text>
    <sha1>98204b5fbe72e229efc8ce3cb4729d0f45b0edbb</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>Onyx4</title>
  <ns>0</ns>
  <id>175</id>
  <revision>
    <id>398</id>
    <timestamp>2025-02-24T21:04:40Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The '''SGI Onyx4''' is a customized Origin 350 with a custom backplane and an ATi-developed graphics system called '''UltimateVision'''.  == Differences from the Onyx 350 == The Onyx4 uses a custom backplane that allows a pair of ATi FireGL graphics cards in lieu of a VPro graphics pipe.   === Compatibility Issues === The Onyx4 uses XFree86 and is incompatible with IRISGL code. Any demos that run in IRISGL are not able to run."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="430" xml:space="preserve">The '''SGI Onyx4''' is a customized Origin 350 with a custom backplane and an ATi-developed graphics system called '''UltimateVision'''.

== Differences from the Onyx 350 ==
The Onyx4 uses a custom backplane that allows a pair of ATi FireGL graphics cards in lieu of a VPro graphics pipe. 

=== Compatibility Issues ===
The Onyx4 uses XFree86 and is incompatible with IRISGL code. Any demos that run in IRISGL are not able to run.</text>
    <sha1>ff7e7e709702f7c2d8f02959e0f62722a5160fa5</sha1>
  </revision>
  <revision>
    <id>399</id>
    <parentid>398</parentid>
    <timestamp>2025-02-24T21:05:14Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="474" xml:space="preserve">The '''SGI Onyx4''' is a customized Origin 350 with a custom backplane and an ATi-developed graphics system called '''UltimateVision'''.

== Differences from the Onyx 350 ==
The Onyx4 uses a custom backplane that allows a pair of ATi FireGL graphics cards in lieu of a VPro graphics pipe. 

=== Compatibility Issues ===
The Onyx4 uses XFree86 and is incompatible with IRISGL code. Any demos that run in IRISGL are not able to run.

[[Category: Hardware]]
[[Category: Stubs]]</text>
    <sha1>24a17084211b338a6525490c44b0f742b9fd9939</sha1>
  </revision>
  <revision>
    <id>400</id>
    <parentid>399</parentid>
    <timestamp>2025-02-24T21:06:33Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="478" xml:space="preserve">The '''SGI Onyx4''' is a customized [[Origin 350]] with a custom backplane and an ATi-developed graphics system called '''UltimateVision'''.

== Differences from the Onyx 350 ==
The Onyx4 uses a custom backplane that allows a pair of ATi FireGL graphics cards in lieu of a VPro graphics pipe. 

=== Compatibility Issues ===
The Onyx4 uses XFree86 and is incompatible with IRISGL code. Any demos that run in IRISGL are not able to run.

[[Category: Hardware]]
[[Category: Stubs]]</text>
    <sha1>e46bbd6c6417c1052a24cd90798834e22b31884b</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>File:Silicon Graphics logo.png</title>
  <ns>6</ns>
  <id>178</id>
  <revision>
    <id>404</id>
    <timestamp>2025-02-24T21:57:40Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16" xml:space="preserve">Classic SGI logo</text>
    <sha1>d4e078992d9fb484b55667419b1fb1f1ded8ea7d</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>Silicon Graphics</title>
  <ns>0</ns>
  <id>138</id>
  <revision>
    <id>405</id>
    <parentid>283</parentid>
    <timestamp>2025-02-24T21:59:13Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2503" xml:space="preserve">[[File:Silicon Graphics logo.png|left|thumb|Classic SGI logo]]
'''Silicon Graphics (SGI)''' was a high performance graphics and computing company founded in 1982 by Jim Clark after leaving his faculty position at Stanford University. It was responsible for many innovations in computer graphics, foundational in the contributions to the early Linux kernel (particularly in the 2000s) and had many close relations with similar companies from the same time period such as Sun MicroSystems, Hewlett Packard, and Digital Equipment Corporation. 
[[File:Sgi later logo.png|thumb|Later SGI logo. ]]

== Early Years ==
SGI in its early years was responsible for the Geometry Engine (The first Very Large Scale Implementation of a geometry pipeline) and its early [[68k-based SGIs (IRIS Series)|IRIS Terminals and Workstations]] share many similarities with the early Sun Multibus systems (and similarly, Sun has its roots in Berkeley University, just as SGI was founded by Stanford faculty and students). The company purchased MIPS Computer Systems and the [[MIPS]] CPU architecture in 1992, after several years of partnership with their R2000 and R3000 CPUs.  In 1988, their 4D1 UNIX system was renamed to [[IRIX]] which retains a massive cult following among UNIX enthusiasts. 

== Success and Growth ==
SGI was responsible for the major CGI developments of the mid-1990s to the early 2000s, as films like [[Jurassic Park]], Titanic, Men in Black, Starship Troopers and Fight Club were all produced using SGI hardware for visual effects. Pixar also made use of SGI hardware after ditching NeXTSTEP in the late 1990s. Ed McCracken (CEO from 1984-1997) was fired in 1997, leading to replacement by Richard Beluzzo. This led to extreme corporate decline as Beluzzo's decisions were chaotic and erratic. 

== Decline ==
SGI continued to hemorrhage money as the purchases of Cray and other organizations were seen as mistakes. Despite Richard Beluzzo's departure in 1999, the company was essentially bankrupt by 2005, and under restructuring, sold the MIPS line and ended SGI development, embracing the [[Itanium]] alliance. Under continuous pressure, SGI went through a chaotic three years, before filing for bankruptcy in 2009. 

== Sale to Rackable Systems ==
[[Rackable Systems]] purchased SGI in 2009, immediately assuming its identity and taking several of its executives for itself. Rackable, DBA "Silicon Graphics International" was purchased in 2016 by Hewlett Packard Enterprise.

[[Category: Companies]]</text>
    <sha1>7dceea219a13b0deee678840dc55ffac04d8fced</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>UNIX</title>
  <ns>0</ns>
  <id>179</id>
  <revision>
    <id>406</id>
    <timestamp>2025-02-24T22:16:08Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "UNIX is a family of preemptive multitasking, multiuser operating systems originating genetically from AT&amp;T UNIX. UNIX was developed between 1969 to 1973 by Bell Labs, then a subsidiary of AT&amp;T, and released, where it became a major force in the business, educational and research markets.   == Variants == Three major genetic types of UNIX are recognized:  * '''Research UNIX''' - The original 10 versions of UNIX developed by Bell Labs * '''Berkeley Software Distribution/Be..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2391" xml:space="preserve">UNIX is a family of preemptive multitasking, multiuser operating systems originating genetically from AT&amp;T UNIX. UNIX was developed between 1969 to 1973 by Bell Labs, then a subsidiary of AT&amp;T, and released, where it became a major force in the business, educational and research markets. 

== Variants ==
Three major genetic types of UNIX are recognized:

* '''Research UNIX''' - The original 10 versions of UNIX developed by Bell Labs
* '''Berkeley Software Distribution/Berkeley UNIX''' - Developed by UC Berkeley, BSD is a derivative of Research UNIX that is notable for several incidental innovations for TCP/IP. 
* '''System III/V UNIX''' - System III is a derivative of UNIX/32V, a research UNIX v7 derivative, which was later developed into System V, which had 5 major releases first under AT&amp;T, and later under SCO/Xinuos.

== UNIX and Silicon Graphics ==
All genetic siblings and parents of IRIX are offsprings of System V Release 3 or 4. [[GL2-2.x]],[[RISC/OS]],  and [[4D1-3.x|4D1 UNIX]] and early [[IRIX 4.0|IRIX]] are System V Release 3, whereas [[IRIX 5.3]] onwards is System V Release 4. 

== Confusion between Trademarks and Genetic UNIX ==
Since the 2000s, the Open Group, a foundation that justifies its existence through UNIX certifications, has aggressively pursued use of the UNIX trademark outside of its "Certified UNIX" which is, moreorless, conforming to the Single UNIX Specification and pay them hundreds of thousands of dollars. This absurd assertion of UNIX certification is evident with the certification of several GNU/Linux derived OSes as well as Apple macOS.

* macOS uses Mach-O, which has never been used by UNIX as a file format, the mach kernel, a small amount of BSD kernel code and libc, but otherwise is either Mach-inspired or original in its design features.  
* GNU/Linux is two projects (a userland/libc and a system kernel) that are not specifically designed for interoperability. While GNU/Linux is closer conceptually to UNIX, it has deviated into its own APIs and conventions since the 2010s and is less and less UNIX-ish as time goes on. This is doubly so for the mobile OSes "Certified UNIX"

Hence, this is a racket by the Open Group. A racket as in "An easy and lucrative moneymaking enterprise, pejorative, to imply illegal or unethical practices." The Open Group sells trademark stickers, nothing more or less.

[[Category: No-Images]]</text>
    <sha1>04cb7aa92f0e539c61e0c56a7c89418dac9d45c5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 17:57:07+00|358">
  <title>Nintendo 64</title>
  <ns>0</ns>
  <id>182</id>
  <revision>
    <id>410</id>
    <timestamp>2025-02-24T23:51:53Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>Created page with "The '''Nintendo 64''' is a game console released in 1996 as the first 64-bit console. In the early 1990s [[Silicon Graphics]] was approached by Nintendo and with their assistance the Nintendo 64, powered by a MIPS VR4300 CPU and several custom co-processors produced by SGI was released. SGI provided the SDK for the Nintendo 64 as well as the microcode for the Reality Display Processor (RDP) and Reality Signal Processor (RSP) chips.   == Specifications == {| class="wikita..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1338" xml:space="preserve">The '''Nintendo 64''' is a game console released in 1996 as the first 64-bit console. In the early 1990s [[Silicon Graphics]] was approached by Nintendo and with their assistance the Nintendo 64, powered by a MIPS VR4300 CPU and several custom co-processors produced by SGI was released. SGI provided the SDK for the Nintendo 64 as well as the microcode for the Reality Display Processor (RDP) and Reality Signal Processor (RSP) chips. 

== Specifications ==
{| class="wikitable"
|+Nintendo 64 Specifications
|CPU
|VR3000
|93.75MHz
|-
|Graphics/Sound
|RSP
|62.5MHz
|-
|RAM
|RAMBUS RDRAM
|4M (Expandable to 8M)
|}
The VR4300 is a modified MIPS R4200 CPU designed for low end embedded applications and licensed to NEC by SGI. It is a full 64-bit design connected to a 32-bit system bus and running o32 ABI code. 

The RCP is split into the RSP and RDP. The RSP is responsible for matrix math, shading, clipping and audio processing. It is a MIPS R4000 with modifications for SIMD. The RDP contains 4Kb of texture memory, and is responsible for Z-buffering, antialiasing, texturing and color combining/blending. 

The RDRAM used by the Nintendo 64 connects through a 16-bit bus and while it's reasonably fast and performant, it has high latency requiring planning and timing to ensure calculations do not get stalled. 

== Development Kit ==</text>
    <sha1>726db4a3342a5f2ed50c012a270b66880b91c31a</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 23:56:31+00|412">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>412</id>
    <parentid>411</parentid>
    <timestamp>2025-02-24T23:56:31Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4580" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation.&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]

'''Resellers'''

• [[SGIDepot]]

• [[Mashek]]

• [http://www.bbsolutions.com/ B&amp;B Solutions]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  [[Visual Workstation Rebrands]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.0 and 5.1]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
		&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''SGI in Popular Culture''' &lt;/div&gt;[[Jurassic Park]]
&lt;/div&gt;  [[Nintendo 64]]
&lt;/div&gt;
			&lt;/div&gt;
		
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


__NOTOC__</text>
    <sha1>5a0a2632b4e7dc48099bae9df0ce4c0fa1b23d38</sha1>
  </revision>
  <revision>
    <id>413</id>
    <parentid>412</parentid>
    <timestamp>2025-02-25T00:16:01Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Development Information */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4597" xml:space="preserve">&lt;div id="mf-home"&gt;
&lt;div id="MainPage"&gt;
	&lt;div id="mp-LeftColumn"&gt;
		&lt;div id="mp-Welcome" class="mp-box mp-wide"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''Welcome to The TechPubs Wiki''' &lt;/div&gt;
				&lt;div class="mp-content"&gt; 
					&lt;small&gt;&lt;center&gt;[[Special:Statistics|{{NUMBEROFARTICLES}}]] [[Special:AllPages|articles]]&lt;/center&gt;&lt;/small&gt;Tech-Pubs.net, or TechPubs, is a public wiki cataloging the hardware of the former Silicon Graphics Corporation.&lt;div class="sharethis-inline-follow-buttons"&gt;&lt;/div&gt;
				&lt;/div&gt;
			&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-WorksColumns" class="mp-box mp-wide"&gt;
		&lt;div id="mp-Games" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Getting Started''' ====
&lt;/div&gt;

===== Setting up IRIX/Familiarization =====
• [[IRIX 101]]

• [[Installing IRIX]]

• [[IRIX Setup 101]]

===== Setting up Software =====
• [[How to Find Commercial Software]]

• [[Open Source Software]] (See Software Section)

===== Communities for Help =====
• [[IRIXNet]]

• [[Reddit]]

• [[SGUG]]

===== Peripherals =====
• [[USB]]

• [[Serial Tablets]]

• [[Tape Drives]]

===== Events =====
• [[Vintage Computer Festival]]

• [[IRIXNet Proposed Swap Meet]]

'''Resellers'''

• [[SGIDepot]]

• [[Mashek]]

• [http://www.bbsolutions.com/ B&amp;B Solutions]
&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-Music" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;
==== '''Hardware''' ====
&lt;/div&gt;

==== 68k-based SGIs (GL2 era) ====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
• [[68k-based SGIs (IRIS Series)]]

==== MIPS-based SGIs (IRIX era) ====
• [[Professional IRIS]]

• [[Personal IRIS]]

• [[IRIS Indigo]]

• [[Power Series]]

• [[Crimson]]

• [[Indy]]

• [[Challenge S]]

• [[Indigo2]]

• [[Onyx]]

• [[Origin 200]]

• [[Onyx2]]

• [[Origin 2000]]

• [[Octane]]

• [[O2]]

• [[Origin 3000]]

• [[Fuel]]

• [[Origin 300]]

•  [[Origin 350]]

•  [[Tezro]]

==== x86-based SGIs ====
•  [[Visual Workstation 320]]

•  [[Visual Workstation 540]]

•  [[Visual Workstation Rebrands]]

===== Itanium (IA-64) based SGIs =====
•  [[SGI 750]]

• [[Altix 350]]

• [[Altix 330]]

• [[Prism]]&lt;/div&gt;
		&lt;/div&gt;
		
		&lt;div id="mp-PrintWorks" class="mp-box mp-tall"&gt;
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-header incell_top"&gt;

==== '''Software''' ====
&lt;/div&gt;

===== IRIX Major Versions =====
&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;• [[IRIX 6.5]]

• [[IRIX 6.2]]

• [[IRIX 5.3]]

• [[IRIX 4.0]]

===== 4D1 Versions =====

• [[4D1-3.x]]

===== GL2 Versions =====
• [[GL2-3.x]]

• [[GL2-2.x]]

===== RISC/OS =====

• [[RISC/OS]]
===== Development Information =====

• [[IRIS Development Option|IRIS Development Option (IRIX 6.2 and prior)]]

• [[MIPSPro|MIPSPro (IRIX 6.5.x)]]

• [[GCC]]

• [[optxeno]]

===== Open Source Distributions =====
• [[SGI Freeware]]

• [[Nekoware]]

• [[SGUG RSE]]

'''IRIX Minor Versions'''

• [[IRIX 5.0 and 5.1]]
&lt;/div&gt;
		&lt;/div&gt;
		&lt;/div&gt;
	&lt;/div&gt;
	&lt;div id="mp-RightColumn"&gt;
		&lt;div id="mp-News" class="mp-box mp-wide"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div class="mp-image mw-no-invert"&gt;&lt;/div&gt;
				&lt;div class="mp-header incell_top"&gt; '''News''' &lt;/div&gt;02/16/2024 - SSL is working and the site is finally feeling "correct" for once!
&lt;/div&gt;
		&lt;/div&gt;
		&lt;div id="mp-Info" class="mp-box"&gt; 
			&lt;div class="mp-innerBox"&gt;
				&lt;div id="mp-Encyclopedia" class="mp-subBox"&gt;
					&lt;div class="mp-header incell_top"&gt; '''Policies And User Info''' &lt;/div&gt;
					&lt;div class="mp-content"&gt; 
						
					[[Style Guide]]&lt;/div&gt;[[TechPubs Wiki:About|About the TechPubs Wiki]]
&lt;/div&gt;    [[TechPubs Wiki:Copyrights|Copyright Information]]&lt;div id="mp-OtherArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Tutorials''' &lt;/div&gt;• [[IRIX 101]]&lt;div class="mp-content"&gt; 
						
					• [[NFS|Setting up NFS]]

&lt;div class="mp-content"&gt; 											• [[How to Find Commercial Software]]
&lt;/div&gt;&lt;div class="mp-content"&gt; 											&lt;/div&gt;&lt;/div&gt;
				&lt;/div&gt;
				&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''Articles Needing Attention''' &lt;/div&gt;[[:Category:Stubs|Stub Articles]]
[[:Category:No-Images|Articles Needing Images]]
&lt;/div&gt;
		&lt;div id="mp-AttentionArticles" class="mp-subBox"&gt;
					&lt;div class="mp-header incell"&gt; '''SGI in Popular Culture''' &lt;/div&gt;[[Jurassic Park]]
&lt;/div&gt;  [[Nintendo 64]]
&lt;/div&gt;
			&lt;/div&gt;
		
		&lt;/div&gt;
	&lt;/div&gt;
&lt;/div&gt;


__NOTOC__</text>
    <sha1>e8db83019ebf71f2e20d681bf8171cf7b5f4edd5</sha1>
  </revision>
</page>
<page arvcontinue="2025-02-24 23:56:31+00|412">
  <title>Nintendo 64</title>
  <ns>0</ns>
  <id>182</id>
  <revision>
    <id>414</id>
    <parentid>410</parentid>
    <timestamp>2025-02-26T01:35:47Z</timestamp>
    <contributor>
      <username>Raion</username>
      <id>1</id>
    </contributor>
    <comment>/* Development Kit */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1589" xml:space="preserve">The '''Nintendo 64''' is a game console released in 1996 as the first 64-bit console. In the early 1990s [[Silicon Graphics]] was approached by Nintendo and with their assistance the Nintendo 64, powered by a MIPS VR4300 CPU and several custom co-processors produced by SGI was released. SGI provided the SDK for the Nintendo 64 as well as the microcode for the Reality Display Processor (RDP) and Reality Signal Processor (RSP) chips. 

== Specifications ==
{| class="wikitable"
|+Nintendo 64 Specifications
|CPU
|VR3000
|93.75MHz
|-
|Graphics/Sound
|RSP
|62.5MHz
|-
|RAM
|RAMBUS RDRAM
|4M (Expandable to 8M)
|}
The VR4300 is a modified MIPS R4200 CPU designed for low end embedded applications and licensed to NEC by SGI. It is a full 64-bit design connected to a 32-bit system bus and running o32 ABI code. 

The RCP is split into the RSP and RDP. The RSP is responsible for matrix math, shading, clipping and audio processing. It is a MIPS R4000 with modifications for SIMD. The RDP contains 4Kb of texture memory, and is responsible for Z-buffering, antialiasing, texturing and color combining/blending. 

The RDRAM used by the Nintendo 64 connects through a 16-bit bus and while it's reasonably fast and performant, it has high latency requiring planning and timing to ensure calculations do not get stalled. 

== Development Kit ==
SGI provided the Nintendo 64 "Emulator Kit" which can be attached to an SGI Indy XL/8 or XL/24. It contains a miniaturized Nintendo 64 and a controller board that went out the back of the Indy. The 5.3/6.2 releases of IRIX are required for operation.</text>
    <sha1>6d4e444182c6c3c1f150bfa7a4b76b5fa108b1c2</sha1>
  </revision>
</page>
</mediawiki>